June 2006 - ntg-pdftex - NTG Mailing Lists

manual issues
by Paweł Jackowski 26 Jul '06

26 Jul '06

Martin, the following primitives are not documented. Could you please comment a status? \pdfpxdimen \pdffirstlineheight \pdflastlinedepth \pdfeachlinedepth \pdfeachlineheight \pdfstrcmp, \pdfmatch % will be replaced by luatex? \pdfretval anything else? Best, -- Pawe/l Jackowski P.Jackowski(a)gust.org.pl

4 5

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