- ntg-pdftex - NTG Mailing Lists

[ pdftex-Feature Requests-572 ] non-compression of pdfxform
by noreply＠sarovar.org 24 Jul '06

24 Jul '06

Feature Requests item #572, was opened at 2006-06-10 23:11 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=572&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: ivo welch (iaw4) Assigned to: Nobody (None) Summary: non-compression of pdfxform Initial Comment: would it be possible to add a feature to avoid compression of the user defined pdfxform stream? [goal: I want to define a string that I can then change via a shell/perl script in the .pdf file itself. I know I have to keep the same number of characters.] \newcount\XOBJA \setbox1=\hbox{12345678909876543210123456789} % this is a special string that one can later replace in the pdf file by hand \pdfxform 1 \XOBJA=\pdflastxform \begin{document} Here is my string on page \arabic{page}: \pdfrefxform \XOBJA \end{document} $ sed 's/12345678909876543210123456789/for user pdftex.../' < myfile.pdf I experimented with setting pdfcompresslevel and resetting it, but it is not reliable in when compression starts. in any case, I do not want the rest at low compression, just my own XOBJ xform. regards, /iaw ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2006-07-25 00:02 Message: Logged In: YES user_id=421 Ivo, sorry for not reacting earlier. Adding this feature seems possible. Is it still needed? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=572&group_id=106

1 0

[ pdftex-Feature Requests-573 ] add \ArtBox to pages
by noreply＠sarovar.org 24 Jul '06

24 Jul '06

Feature Requests item #573, was opened at 2006-06-20 07:32 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=573&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Alexei Gilchrist (alexei2) >Assigned to: Martin Schröder (oneiros) Summary: add \ArtBox to pages Initial Comment: Hi, Is it possible to add an \ArtBox entry to the pages produces by pdftex (with a tight boundingbox)? This way the output of pdftex could be used as input into other progs that use pdf such as a pdf annotating tool. At the moment latex -> dvips -E -> dvitopdf seems to be the only way. thanks, Alexei ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2006-07-24 23:55 Message: Logged In: YES user_id=421 You can already add it manually with \pdfpage{s}attr. But you probably want an automatic entry. Define "tight": pdfTeX knows only the MediaBox (i.e. page dimensions). ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=573&group_id=106

1 0

[ pdftex-Bugs-577 ] Type 3 fonts: on screen fine, on paper filled and displaced
by noreply＠sarovar.org 24 Jul '06

24 Jul '06

Bugs item #577, was opened at 2006-06-28 13:09 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=577&group_id=106 Category: Fonts Group: v1.30.0 Status: Open >Resolution: Works For Me Priority: 5 Submitted By: Peter Dyballa (ballapete) Assigned to: Hartmut Henkel (hhenkel) Summary: Type 3 fonts: on screen fine, on paper filled and displaced Initial Comment: Hello! It's pdfeTeX, Version 3.141592-1.30.4-2.2 (Web2C 7.5.5), on Mac OS X 10.4.6, PPC. The Type 3 font is dijkstra, a famous person's handwriting, as distributed by many SunOS and Solaris versions. Until mid May I had no problem with pdfTeX, dijkstra, and my EPSON EPL-5800 (PostScript 3). This week I again wanted to print a personal letter with Prof. Dijkstra's handwriting used for my letter head. And some letters were filled (P,e,9), others were horizontally and/or vertically displaced from their correct positions. Dijkstra was installed with fontinst. Can this be a pdfTeX problem? End of May I added almost 1 GB of files to update SDKs etc. in Mac OS X to be able to produce Universal Binaries. The last few Tiger versions are known as a bit buggy. My last TeX binaries updates happened in the middle of May, but I have no LOG files from this. The recent LOGs from making the format files contain the string above ... Greetings Pete ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2006-07-24 23:46 Message: Logged In: YES user_id=421 [Sorry for not reacting earlier, but gforge sends no mail when a file is attached; you also have to add a comment.] The attached file uses a Type 1 font and prints perfectly on an Lexmark Optra T612 (which has a PS3 RIP)... ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-06-28 16:09 Message: Logged In: YES user_id=421 Please provide a pdf showing the problems (attach it to this bug). ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=577&group_id=106

1 0

[ pdftex-Patches-580 ] Patch to make ToUnicode for Type1 fonts
by noreply＠sarovar.org 19 Jul '06

19 Jul '06

Patches item #580, was opened at 2006-07-14 20:57 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=580&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: The Thanh Han (hanthethanh) Assigned to: Nobody (None) Summary: Patch to make ToUnicode for Type1 fonts Initial Comment: This is a patch to pdftex so that it can create ToUnicode entries for Type1 fonts. The main purpose is to make ligatures and some other glyphs like smallcap letters or oldstyle digits from OpenType fonts searchable. This patch also contains a minor fix that allows use of fonts without embedding, for example MinionPro or MyriadPro (which are distributed with Acrobat Reader >= 7.0 but from their use is restricted with Acrobat Reader only). How to apply: ~~~~~~~~~~~~~ - this patch applies to the pristine pdftex-1.40.0-beta-20060213 sources only; if you have applied another patch(es) to the sources, please discard them and start from the fresh ones. - how to apply: ,-------- | cd /path/to/pdftex-1.40.0-beta-20060213/src | cat /path/to/the/patch | patch -p1 | ./configure | cd texk/web2c | make pdfetex `-------- If you want to be careful, try the patch with the option '--dry-run' first to see whether the patch can be applied without problems. Usage: ~~~~~~ add the following lines into your document, somewhere at the beginning: ,-------- | \input glyphtounicode.tex | \pdfgentounicode=1 `-------- Customization: ~~~~~~~~~~~~~ If pdftex cannot generate the right ToUnicode value for some glyphs (probably because the glyph name is not ``known'' to pdftex), it's possible to add further entries so pdftex can learn how to generate unicode for such ``unknown'' glyphs. The syntax is simple: \pdfglyphtounicode{<glyph-name>}{<unicode-value>} Example: \pdfglyphtounicode{A}{0041} says that glyph 'A' has its unicode U+0041 The entries in glyphtounicode.tex cover Adobe Glyph List (glyphlist.txt version 2.0) and some addtional glyphs (texglyphlist.txt version 2.33, coming from from lcdf-typetools), plus some additional entries for ligatures. If some glyph name cannot be found, pdftex does some simple name translations: - remove any ".xxx" suffix from glyph name, where "xxx" is a string consisting of alphabetic characters. For example "A.sc" => "A" - remove suffix like "small", "oldstyle", "inferior" and "superior" from glyph name. For example "Asmall" => "A" The result name then is looked up again to find a unicode. Ligatures require a special form of ToUnicode. Example: \pdfglyphtounicode{ff}{00660066} here '0066' is the unicode string for 'f'. Some ligatures have their name like 'f_f_i', in such case the command should be \pdfglyphtounicode{f_f_i}{006600660069} ie '_' is removed from the glyph name, and then all letters are translated to their unicode string. ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2006-07-19 06:08 Message: Logged In: YES user_id=710 patch updated to fix a bug reported by Dohyun Kim ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-07-16 11:19 Message: Logged In: YES user_id=710 patch updated by a bug fix from Akira ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=580&group_id=106

1 0

[ pdftex-Patches-580 ] Patch to make ToUnicode for Type1 fonts
by noreply＠sarovar.org 16 Jul '06

16 Jul '06

Patches item #580, was opened at 2006-07-14 20:57 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=580&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: The Thanh Han (hanthethanh) Assigned to: Nobody (None) Summary: Patch to make ToUnicode for Type1 fonts Initial Comment: This is a patch to pdftex so that it can create ToUnicode entries for Type1 fonts. The main purpose is to make ligatures and some other glyphs like smallcap letters or oldstyle digits from OpenType fonts searchable. This patch also contains a minor fix that allows use of fonts without embedding, for example MinionPro or MyriadPro (which are distributed with Acrobat Reader >= 7.0 but from their use is restricted with Acrobat Reader only). How to apply: ~~~~~~~~~~~~~ - this patch applies to the pristine pdftex-1.40.0-beta-20060213 sources only; if you have applied another patch(es) to the sources, please discard them and start from the fresh ones. - how to apply: ,-------- | cd /path/to/pdftex-1.40.0-beta-20060213/src | cat /path/to/the/patch | patch -p1 | ./configure | cd texk/web2c | make pdfetex `-------- If you want to be careful, try the patch with the option '--dry-run' first to see whether the patch can be applied without problems. Usage: ~~~~~~ add the following lines into your document, somewhere at the beginning: ,-------- | \input glyphtounicode.tex | \pdfgentounicode=1 `-------- Customization: ~~~~~~~~~~~~~ If pdftex cannot generate the right ToUnicode value for some glyphs (probably because the glyph name is not ``known'' to pdftex), it's possible to add further entries so pdftex can learn how to generate unicode for such ``unknown'' glyphs. The syntax is simple: \pdfglyphtounicode{<glyph-name>}{<unicode-value>} Example: \pdfglyphtounicode{A}{0041} says that glyph 'A' has its unicode U+0041 The entries in glyphtounicode.tex cover Adobe Glyph List (glyphlist.txt version 2.0) and some addtional glyphs (texglyphlist.txt version 2.33, coming from from lcdf-typetools), plus some additional entries for ligatures. If some glyph name cannot be found, pdftex does some simple name translations: - remove any ".xxx" suffix from glyph name, where "xxx" is a string consisting of alphabetic characters. For example "A.sc" => "A" - remove suffix like "small", "oldstyle", "inferior" and "superior" from glyph name. For example "Asmall" => "A" The result name then is looked up again to find a unicode. Ligatures require a special form of ToUnicode. Example: \pdfglyphtounicode{ff}{00660066} here '0066' is the unicode string for 'f'. Some ligatures have their name like 'f_f_i', in such case the command should be \pdfglyphtounicode{f_f_i}{006600660069} ie '_' is removed from the glyph name, and then all letters are translated to their unicode string. ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2006-07-16 11:19 Message: Logged In: YES user_id=710 patch updated by a bug fix from Akira ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=580&group_id=106

1 0

[ pdftex-Patches-580 ] Patch to make ToUnicode for Type1 fonts
by noreply＠sarovar.org 14 Jul '06

14 Jul '06

Patches item #580, was opened at 2006-07-14 20:57 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=580&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: The Thanh Han (hanthethanh) Assigned to: Nobody (None) Summary: Patch to make ToUnicode for Type1 fonts Initial Comment: This is a patch to pdftex so that it can create ToUnicode entries for Type1 fonts. The main purpose is to make ligatures and some other glyphs like smallcap letters or oldstyle digits from OpenType fonts searchable. This patch also contains a minor fix that allows use of fonts without embedding, for example MinionPro or MyriadPro (which are distributed with Acrobat Reader >= 7.0 but from their use is restricted with Acrobat Reader only). How to apply: ~~~~~~~~~~~~~ - this patch applies to the pristine pdftex-1.40.0-beta-20060213 sources only; if you have applied another patch(es) to the sources, please discard them and start from the fresh ones. - how to apply: ,-------- | cd /path/to/pdftex-1.40.0-beta-20060213/src | cat /path/to/the/patch | patch -p1 | ./configure | cd texk/web2c | make pdfetex `-------- If you want to be careful, try the patch with the option '--dry-run' first to see whether the patch can be applied without problems. Usage: ~~~~~~ add the following lines into your document, somewhere at the beginning: ,-------- | \input glyphtounicode.tex | \pdfgentounicode=1 `-------- Customization: ~~~~~~~~~~~~~ If pdftex cannot generate the right ToUnicode value for some glyphs (probably because the glyph name is not ``known'' to pdftex), it's possible to add further entries so pdftex can learn how to generate unicode for such ``unknown'' glyphs. The syntax is simple: \pdfglyphtounicode{<glyph-name>}{<unicode-value>} Example: \pdfglyphtounicode{A}{0041} says that glyph 'A' has its unicode U+0041 The entries in glyphtounicode.tex cover Adobe Glyph List (glyphlist.txt version 2.0) and some addtional glyphs (texglyphlist.txt version 2.33, coming from from lcdf-typetools), plus some additional entries for ligatures. If some glyph name cannot be found, pdftex does some simple name translations: - remove any ".xxx" suffix from glyph name, where "xxx" is a string consisting of alphabetic characters. For example "A.sc" => "A" - remove suffix like "small", "oldstyle", "inferior" and "superior" from glyph name. For example "Asmall" => "A" The result name then is looked up again to find a unicode. Ligatures require a special form of ToUnicode. Example: \pdfglyphtounicode{ff}{00660066} here '0066' is the unicode string for 'f'. Some ligatures have their name like 'f_f_i', in such case the command should be \pdfglyphtounicode{f_f_i}{006600660069} ie '_' is removed from the glyph name, and then all letters are translated to their unicode string. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=580&group_id=106

1 0

[ pdftex-Bugs-579 ] The log file is wrapped
by noreply＠sarovar.org 13 Jul '06

13 Jul '06

Bugs item #579, was opened at 2006-07-12 15:17 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=579&group_id=106 Category: web2c Group: v1.30.0 Status: Closed Resolution: Works For Me Priority: 5 Submitted By: Tobias (towolf_) Assigned to: Martin Schröder (oneiros) Summary: The log file is wrapped Initial Comment: [Note that I can’t tell which part of my install is responsible for this] when I compile my source with $ pdflatex source.tex the log that is output is wrapped at column 79, which leads to unfortunate line breaks that make quickfixing my doument harder. Often the line number is split off and escapes my errorformat string for Vim. Can the wrapping be disabled? My Tex distro is Tetex 3 but I compiled pdftex 1.40 beta from source. LaTeX Warning: Reference `sec:method-survey' on page 5 undefined on input line 21. [5] LaTeX Warning: Reference `sec-corpus' on page 6 undefined on input line 58. Package natbib Warning: Citation `Golub2004' on page 6 undefined on input line 60. (/usr/local/share/texmf/tex/latex/lucida/ts1hlh.fd) [6] [7] [8] [9] [10] [11] [12] [13] LaTeX Warning: Reference `sec.res-dec' on page 14 undefined on input line 386. [14] LaTeX Warning: Reference `sec.res-complexity' on page 15 undefined on input lin e 407. ---------------------------------------------------------------------- >Comment By: Tobias (towolf_) Date: 2006-07-13 11:22 Message: Logged In: YES user_id=3729 Thanks Taco, that was what I was looking for. The line that did it (which I had to fish from the the texmf.cnf shipped with the pdftex tarball) was this one: max_print_line = 120 The others had no effect(?). And "line =" was not present in any template I found. And surely, this was not a bug and would have been more appropriately filed as a support request. So merci, I had searched extensively on the web and on newsgroups. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-07-13 08:55 Message: Logged In: YES user_id=421 Still, it isn't a bug in pdfTeX. WorksForMe. :-) ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2006-07-13 08:39 Message: Logged In: YES user_id=1608 In web2c based systems, you can change a set of parameters is texmf.cnf: max_print_error_line = 79 % for tex errors half_error_line = 50 % lhs of tex error context line = 79 % for all other messaging ---------------------------------------------------------------------- Comment By: Hans Hagen (hagen) Date: 2006-07-13 08:01 Message: Logged In: YES user_id=927 i can think of a solution where it is controlled by a variable in the cnf file pdftex.logbreaks=f or so ---------------------------------------------------------------------- Comment By: Tobias (towolf_) Date: 2006-07-12 23:46 Message: Logged In: YES user_id=3729 I see that backwards compatibility is a crucial and laudable aspect of the Tex system. However, when facing my problem I would prefer no wrapping for my log. Is it possible to make a small-scale personal modification and can you point me in the general direction of the place in the source if you think it is? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-07-12 16:15 Message: Logged In: YES user_id=421 The wrapping of lines in the log is a (mis)feature of TeX, so there is nothing we can change about that without breaking compatability. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=579&group_id=106

1 0

[ pdftex-Bugs-579 ] The log file is wrapped
by noreply＠sarovar.org 13 Jul '06

13 Jul '06

Bugs item #579, was opened at 2006-07-12 17:17 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=579&group_id=106 >Category: web2c Group: v1.30.0 Status: Closed >Resolution: Works For Me Priority: 5 Submitted By: Tobias (towolf_) Assigned to: Martin Schröder (oneiros) Summary: The log file is wrapped Initial Comment: [Note that I can’t tell which part of my install is responsible for this] when I compile my source with $ pdflatex source.tex the log that is output is wrapped at column 79, which leads to unfortunate line breaks that make quickfixing my doument harder. Often the line number is split off and escapes my errorformat string for Vim. Can the wrapping be disabled? My Tex distro is Tetex 3 but I compiled pdftex 1.40 beta from source. LaTeX Warning: Reference `sec:method-survey' on page 5 undefined on input line 21. [5] LaTeX Warning: Reference `sec-corpus' on page 6 undefined on input line 58. Package natbib Warning: Citation `Golub2004' on page 6 undefined on input line 60. (/usr/local/share/texmf/tex/latex/lucida/ts1hlh.fd) [6] [7] [8] [9] [10] [11] [12] [13] LaTeX Warning: Reference `sec.res-dec' on page 14 undefined on input line 386. [14] LaTeX Warning: Reference `sec.res-complexity' on page 15 undefined on input lin e 407. ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2006-07-13 10:55 Message: Logged In: YES user_id=421 Still, it isn't a bug in pdfTeX. WorksForMe. :-) ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2006-07-13 10:39 Message: Logged In: YES user_id=1608 In web2c based systems, you can change a set of parameters is texmf.cnf: max_print_error_line = 79 % for tex errors half_error_line = 50 % lhs of tex error context line = 79 % for all other messaging ---------------------------------------------------------------------- Comment By: Hans Hagen (hagen) Date: 2006-07-13 10:01 Message: Logged In: YES user_id=927 i can think of a solution where it is controlled by a variable in the cnf file pdftex.logbreaks=f or so ---------------------------------------------------------------------- Comment By: Tobias (towolf_) Date: 2006-07-13 01:46 Message: Logged In: YES user_id=3729 I see that backwards compatibility is a crucial and laudable aspect of the Tex system. However, when facing my problem I would prefer no wrapping for my log. Is it possible to make a small-scale personal modification and can you point me in the general direction of the place in the source if you think it is? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-07-12 18:15 Message: Logged In: YES user_id=421 The wrapping of lines in the log is a (mis)feature of TeX, so there is nothing we can change about that without breaking compatability. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=579&group_id=106

1 0

[ pdftex-Bugs-579 ] The log file is wrapped
by noreply＠sarovar.org 13 Jul '06

13 Jul '06

Bugs item #579, was opened at 2006-07-12 17:17 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=579&group_id=106 Category: None Group: v1.30.0 Status: Closed Resolution: Rejected Priority: 5 Submitted By: Tobias (towolf_) Assigned to: Martin Schröder (oneiros) Summary: The log file is wrapped Initial Comment: [Note that I can’t tell which part of my install is responsible for this] when I compile my source with $ pdflatex source.tex the log that is output is wrapped at column 79, which leads to unfortunate line breaks that make quickfixing my doument harder. Often the line number is split off and escapes my errorformat string for Vim. Can the wrapping be disabled? My Tex distro is Tetex 3 but I compiled pdftex 1.40 beta from source. LaTeX Warning: Reference `sec:method-survey' on page 5 undefined on input line 21. [5] LaTeX Warning: Reference `sec-corpus' on page 6 undefined on input line 58. Package natbib Warning: Citation `Golub2004' on page 6 undefined on input line 60. (/usr/local/share/texmf/tex/latex/lucida/ts1hlh.fd) [6] [7] [8] [9] [10] [11] [12] [13] LaTeX Warning: Reference `sec.res-dec' on page 14 undefined on input line 386. [14] LaTeX Warning: Reference `sec.res-complexity' on page 15 undefined on input lin e 407. ---------------------------------------------------------------------- >Comment By: Taco Hoekwater (taco) Date: 2006-07-13 10:39 Message: Logged In: YES user_id=1608 In web2c based systems, you can change a set of parameters is texmf.cnf: max_print_error_line = 79 % for tex errors half_error_line = 50 % lhs of tex error context line = 79 % for all other messaging ---------------------------------------------------------------------- Comment By: Hans Hagen (hagen) Date: 2006-07-13 10:01 Message: Logged In: YES user_id=927 i can think of a solution where it is controlled by a variable in the cnf file pdftex.logbreaks=f or so ---------------------------------------------------------------------- Comment By: Tobias (towolf_) Date: 2006-07-13 01:46 Message: Logged In: YES user_id=3729 I see that backwards compatibility is a crucial and laudable aspect of the Tex system. However, when facing my problem I would prefer no wrapping for my log. Is it possible to make a small-scale personal modification and can you point me in the general direction of the place in the source if you think it is? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-07-12 18:15 Message: Logged In: YES user_id=421 The wrapping of lines in the log is a (mis)feature of TeX, so there is nothing we can change about that without breaking compatability. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=579&group_id=106

1 0

[ pdftex-Bugs-579 ] The log file is wrapped
by noreply＠sarovar.org 13 Jul '06

13 Jul '06

Bugs item #579, was opened at 2006-07-12 15:17 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=579&group_id=106 Category: None Group: v1.30.0 Status: Closed Resolution: Rejected Priority: 5 Submitted By: Tobias (towolf_) Assigned to: Martin Schröder (oneiros) Summary: The log file is wrapped Initial Comment: [Note that I can’t tell which part of my install is responsible for this] when I compile my source with $ pdflatex source.tex the log that is output is wrapped at column 79, which leads to unfortunate line breaks that make quickfixing my doument harder. Often the line number is split off and escapes my errorformat string for Vim. Can the wrapping be disabled? My Tex distro is Tetex 3 but I compiled pdftex 1.40 beta from source. LaTeX Warning: Reference `sec:method-survey' on page 5 undefined on input line 21. [5] LaTeX Warning: Reference `sec-corpus' on page 6 undefined on input line 58. Package natbib Warning: Citation `Golub2004' on page 6 undefined on input line 60. (/usr/local/share/texmf/tex/latex/lucida/ts1hlh.fd) [6] [7] [8] [9] [10] [11] [12] [13] LaTeX Warning: Reference `sec.res-dec' on page 14 undefined on input line 386. [14] LaTeX Warning: Reference `sec.res-complexity' on page 15 undefined on input lin e 407. ---------------------------------------------------------------------- >Comment By: Hans Hagen (hagen) Date: 2006-07-13 08:01 Message: Logged In: YES user_id=927 i can think of a solution where it is controlled by a variable in the cnf file pdftex.logbreaks=f or so ---------------------------------------------------------------------- Comment By: Tobias (towolf_) Date: 2006-07-12 23:46 Message: Logged In: YES user_id=3729 I see that backwards compatibility is a crucial and laudable aspect of the Tex system. However, when facing my problem I would prefer no wrapping for my log. Is it possible to make a small-scale personal modification and can you point me in the general direction of the place in the source if you think it is? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-07-12 16:15 Message: Logged In: YES user_id=421 The wrapping of lines in the log is a (mis)feature of TeX, so there is nothing we can change about that without breaking compatability. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=579&group_id=106

1 0

[ pdftex-Bugs-579 ] The log file is wrapped
by noreply＠sarovar.org 12 Jul '06

12 Jul '06

Bugs item #579, was opened at 2006-07-12 15:17 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=579&group_id=106 Category: None Group: v1.30.0 Status: Closed Resolution: Rejected Priority: 5 Submitted By: Tobias (towolf_) Assigned to: Martin Schröder (oneiros) Summary: The log file is wrapped Initial Comment: [Note that I can’t tell which part of my install is responsible for this] when I compile my source with $ pdflatex source.tex the log that is output is wrapped at column 79, which leads to unfortunate line breaks that make quickfixing my doument harder. Often the line number is split off and escapes my errorformat string for Vim. Can the wrapping be disabled? My Tex distro is Tetex 3 but I compiled pdftex 1.40 beta from source. LaTeX Warning: Reference `sec:method-survey' on page 5 undefined on input line 21. [5] LaTeX Warning: Reference `sec-corpus' on page 6 undefined on input line 58. Package natbib Warning: Citation `Golub2004' on page 6 undefined on input line 60. (/usr/local/share/texmf/tex/latex/lucida/ts1hlh.fd) [6] [7] [8] [9] [10] [11] [12] [13] LaTeX Warning: Reference `sec.res-dec' on page 14 undefined on input line 386. [14] LaTeX Warning: Reference `sec.res-complexity' on page 15 undefined on input lin e 407. ---------------------------------------------------------------------- >Comment By: Tobias (towolf_) Date: 2006-07-12 23:46 Message: Logged In: YES user_id=3729 I see that backwards compatibility is a crucial and laudable aspect of the Tex system. However, when facing my problem I would prefer no wrapping for my log. Is it possible to make a small-scale personal modification and can you point me in the general direction of the place in the source if you think it is? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-07-12 16:15 Message: Logged In: YES user_id=421 The wrapping of lines in the log is a (mis)feature of TeX, so there is nothing we can change about that without breaking compatability. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=579&group_id=106

1 0

[ pdftex-Bugs-579 ] The log file is wrapped
by noreply＠sarovar.org 12 Jul '06

12 Jul '06

Bugs item #579, was opened at 2006-07-12 17:17 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=579&group_id=106 Category: None >Group: v1.30.0 >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: Tobias (towolf_) >Assigned to: Martin Schröder (oneiros) Summary: The log file is wrapped Initial Comment: [Note that I can’t tell which part of my install is responsible for this] when I compile my source with $ pdflatex source.tex the log that is output is wrapped at column 79, which leads to unfortunate line breaks that make quickfixing my doument harder. Often the line number is split off and escapes my errorformat string for Vim. Can the wrapping be disabled? My Tex distro is Tetex 3 but I compiled pdftex 1.40 beta from source. LaTeX Warning: Reference `sec:method-survey' on page 5 undefined on input line 21. [5] LaTeX Warning: Reference `sec-corpus' on page 6 undefined on input line 58. Package natbib Warning: Citation `Golub2004' on page 6 undefined on input line 60. (/usr/local/share/texmf/tex/latex/lucida/ts1hlh.fd) [6] [7] [8] [9] [10] [11] [12] [13] LaTeX Warning: Reference `sec.res-dec' on page 14 undefined on input line 386. [14] LaTeX Warning: Reference `sec.res-complexity' on page 15 undefined on input lin e 407. ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2006-07-12 18:15 Message: Logged In: YES user_id=421 The wrapping of lines in the log is a (mis)feature of TeX, so there is nothing we can change about that without breaking compatability. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=579&group_id=106

1 0

[ pdftex-Bugs-579 ] The log file is wrapped
by noreply＠sarovar.org 12 Jul '06

12 Jul '06

Bugs item #579, was opened at 2006-07-12 15:17 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=579&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tobias (towolf_) Assigned to: Nobody (None) Summary: The log file is wrapped Initial Comment: [Note that I can’t tell which part of my install is responsible for this] when I compile my source with $ pdflatex source.tex the log that is output is wrapped at column 79, which leads to unfortunate line breaks that make quickfixing my doument harder. Often the line number is split off and escapes my errorformat string for Vim. Can the wrapping be disabled? My Tex distro is Tetex 3 but I compiled pdftex 1.40 beta from source. LaTeX Warning: Reference `sec:method-survey' on page 5 undefined on input line 21. [5] LaTeX Warning: Reference `sec-corpus' on page 6 undefined on input line 58. Package natbib Warning: Citation `Golub2004' on page 6 undefined on input line 60. (/usr/local/share/texmf/tex/latex/lucida/ts1hlh.fd) [6] [7] [8] [9] [10] [11] [12] [13] LaTeX Warning: Reference `sec.res-dec' on page 14 undefined on input line 386. [14] LaTeX Warning: Reference `sec.res-complexity' on page 15 undefined on input lin e 407. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=579&group_id=106

1 0

1.30.7?
by Martin Schröder 30 Jun '06

30 Jun '06

Hi, the libpng-version we use has a security problem which is fixed in a new version (1.2.12). I'm contemplating doing a new release of 1.30 (1.30.7) incorporating this before leaving for Debrecen on Tuesday. Anything else that _must_ go in? Best Martin

5 8

[ pdftex-Bugs-577 ] Type 3 fonts: on screen fine, on paper filled and displaced
by noreply＠sarovar.org 28 Jun '06

28 Jun '06

Bugs item #577, was opened at 2006-06-28 13:09 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=577&group_id=106 Category: Fonts Group: v1.30.0 Status: Open Resolution: None Priority: 5 Submitted By: Peter Dyballa (ballapete) Assigned to: Hartmut Henkel (hhenkel) Summary: Type 3 fonts: on screen fine, on paper filled and displaced Initial Comment: Hello! It's pdfeTeX, Version 3.141592-1.30.4-2.2 (Web2C 7.5.5), on Mac OS X 10.4.6, PPC. The Type 3 font is dijkstra, a famous person's handwriting, as distributed by many SunOS and Solaris versions. Until mid May I had no problem with pdfTeX, dijkstra, and my EPSON EPL-5800 (PostScript 3). This week I again wanted to print a personal letter with Prof. Dijkstra's handwriting used for my letter head. And some letters were filled (P,e,9), others were horizontally and/or vertically displaced from their correct positions. Dijkstra was installed with fontinst. Can this be a pdfTeX problem? End of May I added almost 1 GB of files to update SDKs etc. in Mac OS X to be able to produce Universal Binaries. The last few Tiger versions are known as a bit buggy. My last TeX binaries updates happened in the middle of May, but I have no LOG files from this. The recent LOGs from making the format files contain the string above ... Greetings Pete ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2006-06-28 16:09 Message: Logged In: YES user_id=421 Please provide a pdf showing the problems (attach it to this bug). ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=577&group_id=106

1 0

[ pdftex-Bugs-577 ] Type 3 fonts: on screen fine, on paper filled and displaced
by noreply＠sarovar.org 28 Jun '06

28 Jun '06

Bugs item #577, was opened at 2006-06-28 13:09 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=577&group_id=106 Category: Fonts Group: v1.30.0 Status: Open Resolution: None Priority: 5 Submitted By: Peter Dyballa (ballapete) Assigned to: Hartmut Henkel (hhenkel) Summary: Type 3 fonts: on screen fine, on paper filled and displaced Initial Comment: Hello! It's pdfeTeX, Version 3.141592-1.30.4-2.2 (Web2C 7.5.5), on Mac OS X 10.4.6, PPC. The Type 3 font is dijkstra, a famous person's handwriting, as distributed by many SunOS and Solaris versions. Until mid May I had no problem with pdfTeX, dijkstra, and my EPSON EPL-5800 (PostScript 3). This week I again wanted to print a personal letter with Prof. Dijkstra's handwriting used for my letter head. And some letters were filled (P,e,9), others were horizontally and/or vertically displaced from their correct positions. Dijkstra was installed with fontinst. Can this be a pdfTeX problem? End of May I added almost 1 GB of files to update SDKs etc. in Mac OS X to be able to produce Universal Binaries. The last few Tiger versions are known as a bit buggy. My last TeX binaries updates happened in the middle of May, but I have no LOG files from this. The recent LOGs from making the format files contain the string above ... Greetings Pete ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=577&group_id=106

1 0

[ pdftex-Feature Requests-573 ] add \ArtBox to pages
by noreply＠sarovar.org 20 Jun '06

20 Jun '06

Feature Requests item #573, was opened at 2006-06-20 05:32 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=573&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Alexei Gilchrist (alexei2) Assigned to: Nobody (None) Summary: add \ArtBox to pages Initial Comment: Hi, Is it possible to add an \ArtBox entry to the pages produces by pdftex (with a tight boundingbox)? This way the output of pdftex could be used as input into other progs that use pdf such as a pdf annotating tool. At the moment latex -> dvips -E -> dvitopdf seems to be the only way. thanks, Alexei ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=573&group_id=106

1 0

[ pdftex-Feature Requests-421 ] \pdf shell escape addition
by noreply＠sarovar.org 12 Jun '06

12 Jun '06

Feature Requests item #421, was opened at 2005-08-26 20:32 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106 Category: None Group: None Status: Open Resolution: Accepted Priority: 5 Submitted By: ivo welch (iaw4) Assigned to: Taco Hoekwater (taco) Summary: \pdf shell escape addition Initial Comment: I would humbly request that in addition add to \write18 ('--shell-escape'), you add a new command, say \input18 (or \pdftexshellinput18), which like \write18 executes a system() command on its argument, but which then pushes the stdout output from this shell command into the stdin stream that TeX is processing. (no, writing to a file and then inputting it does not do the job.) I cannot contribute to the code base of TeX, which seems like black magic to me. But I can offer $300 for this facility. If someone was planning to spend the time to do this anyway, this may push him/her over the margin. However, it is important to me that this enters the standard feature set of pdftex, so that it will persist through future versions, so this would be part of the bargain here. regards, /ivo welch ---------------------------------------------------------------------- >Comment By: Taco Hoekwater (taco) Date: 2006-06-12 20:11 Message: Logged In: YES user_id=1608 > i.e. even \immediate\closeout doesn't make the file > immediately visible and fully readable? > isn't this a bug, if it is so? it is a bug in certain operating systems, not in TeX ;-) > btw, how will this work in case of non-immediate > \openin and \openout? (in case they will end up executed > during the \shipout?) The pipes will be opened (and closed, hopefully) during shipout, not before (just like normal '\openout' files). ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-06-12 18:49 Message: Logged In: NO > one of the reasons why intermediate files don't work > is that it interferes with flushing of files > [and the moment that files are seen] i.e. even \immediate\closeout doesn't make the file immediately visible and fully readable? isn't this a bug, if it is so? nevertheless, the Taco's implementation of this feature is nice; btw, how will this work in case of non-immediate \openin and \openout? (in case they will end up executed during the \shipout?) ---------------------------------------------------------------------- Comment By: Hans Hagen (hagen) Date: 2006-06-12 11:08 Message: Logged In: YES user_id=927 it may interest you that taco, fabrice an i have been playing with piping the last couple of weeks; we're still struggling with decent ways to get around operating system related problems; in order for such a feature (actually more generic that you suggest) to work, it must be cross platform; btw, one of the reasons why intermediate files don't work is that it interferes with flushing of files [and the moment that files are seen] Hans ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2006-06-11 15:36 Message: Logged In: YES user_id=1608 Hi Ivo, Sorry, I had completely forgotten about this. Attached is a (preliminary?) patch for openclose.c (in the texk/web2c/lib directory) that gives this functionality. It is a really simple thing: if the first character of a filename for \openin or \openout is a pipe symbol (|), the filename is assumed to be a request for a pipe to a command line that is given in the rest of the filename. Of course, you need "shell_escape = t" in your texmf.cnf for this to work. And whether or not this makes it to the distribution(s) is not up to me, of course. Have fun, Taco ------------------- Two small examples: \openin1= "|ls -l" \loop \unless \ifeof1 \read1 to \cs \message{\meaning\cs} \repeat \openout1= "|sort >alphabet.tex" \write1{b} \write1{a} \write1{c} \closeout1 \bye ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-06-11 04:58 Message: Logged In: NO could you please clarify why "no, writing to a file and then inputting it does not do the job"? ---------------------------------------------------------------------- Comment By: ivo welch (iaw4) Date: 2006-06-10 23:05 Message: Logged In: YES user_id=2771 any chance this will happen, taco? regards, /ivo ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2005-08-27 09:01 Message: Logged In: YES user_id=1608 I have an idea on how to do this, so I've assigned it to myself ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106

1 0

[ pdftex-Feature Requests-421 ] \pdf shell escape addition
by noreply＠sarovar.org 12 Jun '06

12 Jun '06

Feature Requests item #421, was opened at 2005-08-27 00:02 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106 Category: None Group: None Status: Open Resolution: Accepted Priority: 5 Submitted By: ivo welch (iaw4) Assigned to: Taco Hoekwater (taco) Summary: \pdf shell escape addition Initial Comment: I would humbly request that in addition add to \write18 ('--shell-escape'), you add a new command, say \input18 (or \pdftexshellinput18), which like \write18 executes a system() command on its argument, but which then pushes the stdout output from this shell command into the stdin stream that TeX is processing. (no, writing to a file and then inputting it does not do the job.) I cannot contribute to the code base of TeX, which seems like black magic to me. But I can offer $300 for this facility. If someone was planning to spend the time to do this anyway, this may push him/her over the margin. However, it is important to me that this enters the standard feature set of pdftex, so that it will persist through future versions, so this would be part of the bargain here. regards, /ivo welch ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-06-12 22:19 Message: Logged In: NO > one of the reasons why intermediate files don't work > is that it interferes with flushing of files > [and the moment that files are seen] i.e. even \immediate\closeout doesn't make the file immediately visible and fully readable? isn't this a bug, if it is so? nevertheless, the Taco's implementation of this feature is nice; btw, how will this work in case of non-immediate \openin and \openout? (in case they will end up executed during the \shipout?) ---------------------------------------------------------------------- Comment By: Hans Hagen (hagen) Date: 2006-06-12 14:38 Message: Logged In: YES user_id=927 it may interest you that taco, fabrice an i have been playing with piping the last couple of weeks; we're still struggling with decent ways to get around operating system related problems; in order for such a feature (actually more generic that you suggest) to work, it must be cross platform; btw, one of the reasons why intermediate files don't work is that it interferes with flushing of files [and the moment that files are seen] Hans ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2006-06-11 19:06 Message: Logged In: YES user_id=1608 Hi Ivo, Sorry, I had completely forgotten about this. Attached is a (preliminary?) patch for openclose.c (in the texk/web2c/lib directory) that gives this functionality. It is a really simple thing: if the first character of a filename for \openin or \openout is a pipe symbol (|), the filename is assumed to be a request for a pipe to a command line that is given in the rest of the filename. Of course, you need "shell_escape = t" in your texmf.cnf for this to work. And whether or not this makes it to the distribution(s) is not up to me, of course. Have fun, Taco ------------------- Two small examples: \openin1= "|ls -l" \loop \unless \ifeof1 \read1 to \cs \message{\meaning\cs} \repeat \openout1= "|sort >alphabet.tex" \write1{b} \write1{a} \write1{c} \closeout1 \bye ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-06-11 08:28 Message: Logged In: NO could you please clarify why "no, writing to a file and then inputting it does not do the job"? ---------------------------------------------------------------------- Comment By: ivo welch (iaw4) Date: 2006-06-11 02:35 Message: Logged In: YES user_id=2771 any chance this will happen, taco? regards, /ivo ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2005-08-27 12:31 Message: Logged In: YES user_id=1608 I have an idea on how to do this, so I've assigned it to myself ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106

1 0

[ pdftex-Feature Requests-421 ] \pdf shell escape addition
by noreply＠sarovar.org 12 Jun '06

12 Jun '06

Feature Requests item #421, was opened at 2005-08-26 18:32 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106 Category: None Group: None Status: Open Resolution: Accepted Priority: 5 Submitted By: ivo welch (iaw4) Assigned to: Taco Hoekwater (taco) Summary: \pdf shell escape addition Initial Comment: I would humbly request that in addition add to \write18 ('--shell-escape'), you add a new command, say \input18 (or \pdftexshellinput18), which like \write18 executes a system() command on its argument, but which then pushes the stdout output from this shell command into the stdin stream that TeX is processing. (no, writing to a file and then inputting it does not do the job.) I cannot contribute to the code base of TeX, which seems like black magic to me. But I can offer $300 for this facility. If someone was planning to spend the time to do this anyway, this may push him/her over the margin. However, it is important to me that this enters the standard feature set of pdftex, so that it will persist through future versions, so this would be part of the bargain here. regards, /ivo welch ---------------------------------------------------------------------- >Comment By: Hans Hagen (hagen) Date: 2006-06-12 09:08 Message: Logged In: YES user_id=927 it may interest you that taco, fabrice an i have been playing with piping the last couple of weeks; we're still struggling with decent ways to get around operating system related problems; in order for such a feature (actually more generic that you suggest) to work, it must be cross platform; btw, one of the reasons why intermediate files don't work is that it interferes with flushing of files [and the moment that files are seen] Hans ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2006-06-11 13:36 Message: Logged In: YES user_id=1608 Hi Ivo, Sorry, I had completely forgotten about this. Attached is a (preliminary?) patch for openclose.c (in the texk/web2c/lib directory) that gives this functionality. It is a really simple thing: if the first character of a filename for \openin or \openout is a pipe symbol (|), the filename is assumed to be a request for a pipe to a command line that is given in the rest of the filename. Of course, you need "shell_escape = t" in your texmf.cnf for this to work. And whether or not this makes it to the distribution(s) is not up to me, of course. Have fun, Taco ------------------- Two small examples: \openin1= "|ls -l" \loop \unless \ifeof1 \read1 to \cs \message{\meaning\cs} \repeat \openout1= "|sort >alphabet.tex" \write1{b} \write1{a} \write1{c} \closeout1 \bye ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-06-11 02:58 Message: Logged In: NO could you please clarify why "no, writing to a file and then inputting it does not do the job"? ---------------------------------------------------------------------- Comment By: ivo welch (iaw4) Date: 2006-06-10 21:05 Message: Logged In: YES user_id=2771 any chance this will happen, taco? regards, /ivo ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2005-08-27 07:01 Message: Logged In: YES user_id=1608 I have an idea on how to do this, so I've assigned it to myself ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106

1 0

[ pdftex-Feature Requests-421 ] \pdf shell escape addition
by noreply＠sarovar.org 11 Jun '06

11 Jun '06

Feature Requests item #421, was opened at 2005-08-26 20:32 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106 Category: None Group: None Status: Open Resolution: Accepted Priority: 5 Submitted By: ivo welch (iaw4) Assigned to: Taco Hoekwater (taco) Summary: \pdf shell escape addition Initial Comment: I would humbly request that in addition add to \write18 ('--shell-escape'), you add a new command, say \input18 (or \pdftexshellinput18), which like \write18 executes a system() command on its argument, but which then pushes the stdout output from this shell command into the stdin stream that TeX is processing. (no, writing to a file and then inputting it does not do the job.) I cannot contribute to the code base of TeX, which seems like black magic to me. But I can offer $300 for this facility. If someone was planning to spend the time to do this anyway, this may push him/her over the margin. However, it is important to me that this enters the standard feature set of pdftex, so that it will persist through future versions, so this would be part of the bargain here. regards, /ivo welch ---------------------------------------------------------------------- >Comment By: Taco Hoekwater (taco) Date: 2006-06-11 15:36 Message: Logged In: YES user_id=1608 Hi Ivo, Sorry, I had completely forgotten about this. Attached is a (preliminary?) patch for openclose.c (in the texk/web2c/lib directory) that gives this functionality. It is a really simple thing: if the first character of a filename for \openin or \openout is a pipe symbol (|), the filename is assumed to be a request for a pipe to a command line that is given in the rest of the filename. Of course, you need "shell_escape = t" in your texmf.cnf for this to work. And whether or not this makes it to the distribution(s) is not up to me, of course. Have fun, Taco ------------------- Two small examples: \openin1= "|ls -l" \loop \unless \ifeof1 \read1 to \cs \message{\meaning\cs} \repeat \openout1= "|sort >alphabet.tex" \write1{b} \write1{a} \write1{c} \closeout1 \bye ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-06-11 04:58 Message: Logged In: NO could you please clarify why "no, writing to a file and then inputting it does not do the job"? ---------------------------------------------------------------------- Comment By: ivo welch (iaw4) Date: 2006-06-10 23:05 Message: Logged In: YES user_id=2771 any chance this will happen, taco? regards, /ivo ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2005-08-27 09:01 Message: Logged In: YES user_id=1608 I have an idea on how to do this, so I've assigned it to myself ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106

1 0

[ pdftex-Feature Requests-421 ] \pdf shell escape addition
by noreply＠sarovar.org 11 Jun '06

11 Jun '06

Feature Requests item #421, was opened at 2005-08-27 00:02 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106 Category: None Group: None Status: Open Resolution: Accepted Priority: 5 Submitted By: ivo welch (iaw4) Assigned to: Taco Hoekwater (taco) Summary: \pdf shell escape addition Initial Comment: I would humbly request that in addition add to \write18 ('--shell-escape'), you add a new command, say \input18 (or \pdftexshellinput18), which like \write18 executes a system() command on its argument, but which then pushes the stdout output from this shell command into the stdin stream that TeX is processing. (no, writing to a file and then inputting it does not do the job.) I cannot contribute to the code base of TeX, which seems like black magic to me. But I can offer $300 for this facility. If someone was planning to spend the time to do this anyway, this may push him/her over the margin. However, it is important to me that this enters the standard feature set of pdftex, so that it will persist through future versions, so this would be part of the bargain here. regards, /ivo welch ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-06-11 08:28 Message: Logged In: NO could you please clarify why "no, writing to a file and then inputting it does not do the job"? ---------------------------------------------------------------------- Comment By: ivo welch (iaw4) Date: 2006-06-11 02:35 Message: Logged In: YES user_id=2771 any chance this will happen, taco? regards, /ivo ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2005-08-27 12:31 Message: Logged In: YES user_id=1608 I have an idea on how to do this, so I've assigned it to myself ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106

1 0

[ pdftex-Feature Requests-572 ] non-compression of pdfxform
by noreply＠sarovar.org 10 Jun '06

10 Jun '06

Feature Requests item #572, was opened at 2006-06-10 21:11 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=572&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: ivo welch (iaw4) Assigned to: Nobody (None) Summary: non-compression of pdfxform Initial Comment: would it be possible to add a feature to avoid compression of the user defined pdfxform stream? [goal: I want to define a string that I can then change via a shell/perl script in the .pdf file itself. I know I have to keep the same number of characters.] \newcount\XOBJA \setbox1=\hbox{12345678909876543210123456789} % this is a special string that one can later replace in the pdf file by hand \pdfxform 1 \XOBJA=\pdflastxform \begin{document} Here is my string on page \arabic{page}: \pdfrefxform \XOBJA \end{document} $ sed 's/12345678909876543210123456789/for user pdftex.../' < myfile.pdf I experimented with setting pdfcompresslevel and resetting it, but it is not reliable in when compression starts. in any case, I do not want the rest at low compression, just my own XOBJ xform. regards, /iaw ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=572&group_id=106

1 0

[ pdftex-Feature Requests-421 ] \pdf shell escape addition
by noreply＠sarovar.org 10 Jun '06

10 Jun '06

Feature Requests item #421, was opened at 2005-08-26 18:32 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106 Category: None Group: None Status: Open Resolution: Accepted Priority: 5 Submitted By: ivo welch (iaw4) Assigned to: Taco Hoekwater (taco) Summary: \pdf shell escape addition Initial Comment: I would humbly request that in addition add to \write18 ('--shell-escape'), you add a new command, say \input18 (or \pdftexshellinput18), which like \write18 executes a system() command on its argument, but which then pushes the stdout output from this shell command into the stdin stream that TeX is processing. (no, writing to a file and then inputting it does not do the job.) I cannot contribute to the code base of TeX, which seems like black magic to me. But I can offer $300 for this facility. If someone was planning to spend the time to do this anyway, this may push him/her over the margin. However, it is important to me that this enters the standard feature set of pdftex, so that it will persist through future versions, so this would be part of the bargain here. regards, /ivo welch ---------------------------------------------------------------------- >Comment By: ivo welch (iaw4) Date: 2006-06-10 21:05 Message: Logged In: YES user_id=2771 any chance this will happen, taco? regards, /ivo ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2005-08-27 07:01 Message: Logged In: YES user_id=1608 I have an idea on how to do this, so I've assigned it to myself ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106

1 0

[ pdftex-Bugs-565 ] ttf2afm fails to include characters specified with uniXXXX
by noreply＠sarovar.org 29 May '06

29 May '06

Bugs item #565, was opened at 2006-05-29 14:37 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=565&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mike Spivey (spivey) Assigned to: Nobody (None) Summary: ttf2afm fails to include characters specified with uniXXXX Initial Comment: If characters are specified in an encoding vector as uniXXXX (with XXXX a hexadecimal unicode value), then these characters are not included in the AFM output, unlike characters that are specified by name. The same goes for characters specifed by position. A suggested patch is attached. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=565&group_id=106

1 0