September 2007 - ntg-pdftex - NTG Mailing Lists

[ pdftex-Patches-864 ] \suppressfontnotfounderror patch
by noreply＠sarovar.org 18 Sep '07

18 Sep '07

Patches item #864, was opened at 2007-09-17 17:49 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=864&group_id=106 Category: Primitives Group: v1.50.0 Status: Open Resolution: Accepted Priority: 5 Submitted By: Taco Hoekwater (taco) Assigned to: Martin Schröder (oneiros) Summary: \suppressfontnotfounderror patch Initial Comment: Attached is a patch for pdftex 1.50 (current trunk) that introduces a new integer parameter named \suppressfontnotfounderror. If this parameter is non-zero, then (pdf)tex will not complain about font metric files that are not found, but silently skip the font assignment, making the requested csname \ifx-equal to \nullfont. The purpose is to allow macro programmers a way to gracefully recover from a missing or differently named font. I am aware there is a trick that uses \batchmode to test for font existance, but the downside of that is that it calls TeX's error() routine, which clobbers the executable's return value. That makes it a no-no in "make"-like environments where the return value of TeX is checked to decide on further actions. This functionality will also be added to the next versions of xetex and luatex (that's why the name does not start with \pdf...). % simple example usage \def\testfont#1{% \font\junk=#1 \ifx\junk\nullfont \message{Font #1 not found} \else \message{Font #1 found} \fi } {\suppressfontnotfounderror=1 \testfont{cmr-junk} } \bye ---------------------------------------------------------------------- >Comment By: Taco Hoekwater (taco) Date: 2007-09-18 08:10 Message: Logged In: YES user_id=1608 Well, at least it does not affect the tex user directly: there is a stream of garbage on the screen and that looks ugly, but there is no error interaction, and the system-level return value of pdftex is unaffected. I don't know if there is a clean way to control mktextfm cs, but if it can be done, that would be a nice addition to the web2c change file. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-09-17 21:53 Message: Logged In: YES user_id=421 IMHO it works only somuch, but that may be due to kpathsea: > pdftex test.tex This is pdfTeX, Version 3.141592-1.50.0-alpha-20070917 (Web2C 7.5.6) entering extended mode (./test.texkpathsea: Running mktextfm cmr-junk mktextfm: Running mf-nowin -progname=mf \mode:=lexmarkr; mag:=1; nonstopmode; input cmr-junk This is METAFONT, Version 2.71828 (Web2C 7.5.4) kpathsea: Running mktexmf cmr-junk ! I can't find file `cmr-junk'. <*> ...xmarkr; mag:=1; nonstopmode; input cmr-junk Please type another input file name ! Emergency stop. <*> ...xmarkr; mag:=1; nonstopmode; input cmr-junk Transcript written on mfput.log. grep: cmr-junk.log: Datei oder Verzeichnis nicht gefunden mktextfm: `mf-nowin -progname=mf \mode:=lexmarkr; mag:=1; nonstopmode; input cmr-junk' failed to make cmr-junk.tfm. kpathsea: Appending font creation commands to missfont.log. Font cmr-junk not found ) No pages of output. Transcript written on test.log. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=864&group_id=106

1 0

[ pdftex-Patches-864 ] \suppressfontnotfounderror patch
by noreply＠sarovar.org 17 Sep '07

17 Sep '07

Patches item #864, was opened at 2007-09-17 17:49 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=864&group_id=106 Category: Primitives Group: v1.50.0 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Taco Hoekwater (taco) >Assigned to: Martin Schröder (oneiros) Summary: \suppressfontnotfounderror patch Initial Comment: Attached is a patch for pdftex 1.50 (current trunk) that introduces a new integer parameter named \suppressfontnotfounderror. If this parameter is non-zero, then (pdf)tex will not complain about font metric files that are not found, but silently skip the font assignment, making the requested csname \ifx-equal to \nullfont. The purpose is to allow macro programmers a way to gracefully recover from a missing or differently named font. I am aware there is a trick that uses \batchmode to test for font existance, but the downside of that is that it calls TeX's error() routine, which clobbers the executable's return value. That makes it a no-no in "make"-like environments where the return value of TeX is checked to decide on further actions. This functionality will also be added to the next versions of xetex and luatex (that's why the name does not start with \pdf...). % simple example usage \def\testfont#1{% \font\junk=#1 \ifx\junk\nullfont \message{Font #1 not found} \else \message{Font #1 found} \fi } {\suppressfontnotfounderror=1 \testfont{cmr-junk} } \bye ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-09-17 21:53 Message: Logged In: YES user_id=421 IMHO it works only somuch, but that may be due to kpathsea: > pdftex test.tex This is pdfTeX, Version 3.141592-1.50.0-alpha-20070917 (Web2C 7.5.6) entering extended mode (./test.texkpathsea: Running mktextfm cmr-junk mktextfm: Running mf-nowin -progname=mf \mode:=lexmarkr; mag:=1; nonstopmode; input cmr-junk This is METAFONT, Version 2.71828 (Web2C 7.5.4) kpathsea: Running mktexmf cmr-junk ! I can't find file `cmr-junk'. <*> ...xmarkr; mag:=1; nonstopmode; input cmr-junk Please type another input file name ! Emergency stop. <*> ...xmarkr; mag:=1; nonstopmode; input cmr-junk Transcript written on mfput.log. grep: cmr-junk.log: Datei oder Verzeichnis nicht gefunden mktextfm: `mf-nowin -progname=mf \mode:=lexmarkr; mag:=1; nonstopmode; input cmr-junk' failed to make cmr-junk.tfm. kpathsea: Appending font creation commands to missfont.log. Font cmr-junk not found ) No pages of output. Transcript written on test.log. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=864&group_id=106

1 0

[ pdftex-Patches-864 ] \suppressfontnotfounderror patch
by noreply＠sarovar.org 17 Sep '07

17 Sep '07

Patches item #864, was opened at 2007-09-17 17:49 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=864&group_id=106 >Category: Primitives >Group: v1.50.0 Status: Open Resolution: None Priority: 5 Submitted By: Taco Hoekwater (taco) Assigned to: Nobody (None) Summary: \suppressfontnotfounderror patch Initial Comment: Attached is a patch for pdftex 1.50 (current trunk) that introduces a new integer parameter named \suppressfontnotfounderror. If this parameter is non-zero, then (pdf)tex will not complain about font metric files that are not found, but silently skip the font assignment, making the requested csname \ifx-equal to \nullfont. The purpose is to allow macro programmers a way to gracefully recover from a missing or differently named font. I am aware there is a trick that uses \batchmode to test for font existance, but the downside of that is that it calls TeX's error() routine, which clobbers the executable's return value. That makes it a no-no in "make"-like environments where the return value of TeX is checked to decide on further actions. This functionality will also be added to the next versions of xetex and luatex (that's why the name does not start with \pdf...). % simple example usage \def\testfont#1{% \font\junk=#1 \ifx\junk\nullfont \message{Font #1 not found} \else \message{Font #1 found} \fi } {\suppressfontnotfounderror=1 \testfont{cmr-junk} } \bye ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=864&group_id=106

1 0

[ pdftex-Patches-864 ] \suppressfontnotfounderror patch
by noreply＠sarovar.org 17 Sep '07

17 Sep '07

Patches item #864, was opened at 2007-09-17 17:49 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=864&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Taco Hoekwater (taco) Assigned to: Nobody (None) Summary: \suppressfontnotfounderror patch Initial Comment: Attached is a patch for pdftex 1.50 (current trunk) that introduces a new integer parameter named \suppressfontnotfounderror. If this parameter is non-zero, then (pdf)tex will not complain about font metric files that are not found, but silently skip the font assignment, making the requested csname \ifx-equal to \nullfont. The purpose is to allow macro programmers a way to gracefully recover from a missing or differently named font. I am aware there is a trick that uses \batchmode to test for font existance, but the downside of that is that it calls TeX's error() routine, which clobbers the executable's return value. That makes it a no-no in "make"-like environments where the return value of TeX is checked to decide on further actions. This functionality will also be added to the next versions of xetex and luatex (that's why the name does not start with \pdf...). % simple example usage \def\testfont#1{% \font\junk=#1 \ifx\junk\nullfont \message{Font #1 not found} \else \message{Font #1 found} \fi } {\suppressfontnotfounderror=1 \testfont{cmr-junk} } \bye ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=864&group_id=106

1 0

\nofontnotfounderror patch
by Taco Hoekwater 17 Sep '07

17 Sep '07

Hi, Attached is a patch for pdftex 1.50 (current trunk) that introduces a new integer parameter named \nofontnotfounderror. If this parameter is non-zero, then (pdf)tex will not complain about font metric files that are not found, but silently skip the font assignment, making the requested csname \ifx-equal to \nullfont. The purpose is to allow macro programmers a way to gracefully recover from a missing or differently named font. I am aware there is a trick that uses \batchmode to test for font existance, but the downside of that is that it calls TeX's error() routine, which clobbers the executable's return value. That makes it a no-no in "make"-like environments where the return value of TeX is checked to decide on further actions. This functionality will also be added to the next versions of xetex and luatex (that's why the name does not start with \pdf...). % simple example usage \def\testfont#1{% \font\junk=#1 \ifx\junk\nullfont \message{Font #1 not found} \else \message{Font #1 found} \fi } {\nofontnotfounderror=1 \testfont{cmr-junk} } \bye Best wishes, Taco PS Martin, what is the status on the trackers? I did not know whether to use sarovar or to enable the one on supelec, that's why it is now on the mailing list.

2 2

[ pdftex-Bugs-861 ] including encrypted pdf
by noreply＠sarovar.org 09 Sep '07

09 Sep '07

Bugs item #861, was opened at 2007-09-07 10:35 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=861&group_id=106 Category: xpdf Group: v1.40.5 Status: Open Resolution: Accepted Priority: 5 Submitted By: Herbert Voss (voss) Assigned to: Martin Schröder (oneiros) Summary: including encrypted pdf Initial Comment: when i insert a page of the http://tug.org/texshowcase/en_gb_eclipse_114.pdf with \documentclass{article} \usepackage{graphicx} \begin{document} \includegraphics[page=1]{en_gb_eclipse_114} \end{document} I'll get an empty page with pdftex 1.40.5 With version 1.40.3 (xpdf 3.01) everything is fine. There is no difference in both logfiles. ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-09-09 20:44 Message: Logged In: YES user_id=421 It also works with 1.40.5 and libs/xpdf from 1.40.3, so the problem is either in xpdf or in our binding. We have contacted Derek. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=861&group_id=106

1 0

[ pdftex-Bugs-861 ] including encrypted pdf
by noreply＠sarovar.org 07 Sep '07

07 Sep '07

Bugs item #861, was opened at 2007-09-07 10:35 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=861&group_id=106 Category: xpdf >Group: v1.40.5 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Herbert Voss (voss) Assigned to: Martin Schröder (oneiros) Summary: including encrypted pdf Initial Comment: when i insert a page of the http://tug.org/texshowcase/en_gb_eclipse_114.pdf with \documentclass{article} \usepackage{graphicx} \begin{document} \includegraphics[page=1]{en_gb_eclipse_114} \end{document} I'll get an empty page with pdftex 1.40.5 With version 1.40.3 (xpdf 3.01) everything is fine. There is no difference in both logfiles. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=861&group_id=106

1 0

[ pdftex-Bugs-861 ] including encrypted pdf
by noreply＠sarovar.org 07 Sep '07

07 Sep '07

Bugs item #861, was opened at 2007-09-07 08:35 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=861&group_id=106 Category: xpdf Group: None Status: Open Resolution: None Priority: 5 Submitted By: Herbert Voss (voss) Assigned to: Martin Schröder (oneiros) Summary: including encrypted pdf Initial Comment: when i insert a page of the http://tug.org/texshowcase/en_gb_eclipse_114.pdf with \documentclass{article} \usepackage{graphicx} \begin{document} \includegraphics[page=1]{en_gb_eclipse_114} \end{document} I'll get an empty page with pdftex 1.40.5 With version 1.40.3 (xpdf 3.01) everything is fine. There is no difference in both logfiles. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=861&group_id=106

1 0