- ntg-pdftex - NTG Mailing Lists

[ pdftex-Bugs-102 ] \pdffontexpand without autoexpand produces strange "ligature"
by noreply＠sarovar.org 01 Sep '04

01 Sep '04

Bugs item #102, was opened at 2004-08-20 18:38 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=102&group_id=106 Category: hz Group: v1.20a >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: The Thanh Han (hanthethanh) >Summary: \pdffontexpand without autoexpand produces strange "ligature" Initial Comment: In the attached test file the fonts are set up by \def\setupfont{ \resetefcode\font \pdffontexpand\font 20 20 5 %autoexpand } This produces a strange "ligature" in the fifth word of the resulting pdf (test/oertzen.pdf): instead of "ä" in "Verhältnis" something quite different is printed. If autoexpand is used, "ä" is printed. Also the log shows control characters at some points in the trace of the first page, most notably in the fonts names (0a and 00). ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2004-09-01 17:34 Message: Logged In: YES user_id=421 Closed; not a pdftex problem, but a broken font. ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2004-08-26 19:27 Message: Logged In: NO I don't think this is a pdftex bug. The virtual font is broken. You get the same result with this plain tex file: ----------------------------------- \font\testfont=pegri9d+20\testfont ä ö ü \char199 \char172 \char185 \char177 \char208 \char174 \char199 \bye ----------------------------------- Running > vftovp pegri9d+20.vf pegri9d+20.tfm test.vp will report some of the broken characters. Regards, Robert. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2004-08-20 18:40 Message: Logged In: YES user_id=421 I tried this with pdfetex and pdftex (not etex), and the effect is the same. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=102&group_id=106

1 0

[ pdftex-Bugs-103 ] pdftex crashes when including a file featuring auto expansion
by noreply＠sarovar.org 27 Aug '04

27 Aug '04

Bugs item #103, was opened at 2004-08-26 22:56 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=103&group_id=106 Category: PDF inclusion Group: v1.20a Status: Closed Resolution: Works For Me Priority: 5 Submitted By: Nobody (None) Assigned to: Martin Schröder (oneiros) Summary: pdftex crashes when including a file featuring auto expansion Initial Comment: When including a pdf file that contains fonts created with the autoexpand feature, pdftex will crash on the including file. This does not happen if the expanded fonts are available. Neither does it occur with the base 35 fonts (well, I've only tested ptmr8r and phvr8r). Test case below. Regards, Robert. plain tex file to be included (let's call it include.tex): -------------------------------------------- \font\testfont=cmr10\testfont \pdfadjustspacing2 \pdffontexpand\font 20 20 5 autoexpand \hsize=15em Some characters that pretend to make up words which pretend to make sense. \bye -------------------------------------------- latex file on which pdftex crashes: -------------------------------------------- \documentclass{minimal} \usepackage{graphics} \begin{document} \tracingall \includegraphics{include.pdf} \end{document} -------------------------------------------- last lines of the online log (no log file created): -------------------------------------------- Completed box being shipped out [1] \vbox(578.15999+0.0)x469.75499 .\glue 0.0 .\vbox(578.15999+0.0)x469.75499 ..\vbox(0.0+0.0)x469.75499 ...\glue 0.0 plus 1.0fil ...\hbox(0.0+0.0)x469.75499 ..\glue 0.0 ..\glue(\lineskip) 0.0 ..\vbox(578.15999+0.0)x469.75499 ...\glue(\topskip) 0.0 ...\hbox(845.04504+0.0)x469.75499 ....\hbox(0.0+0.0)x20.0 ....\hbox(845.04504+0.0)x597.50682 .....\hbox(845.0471+0.0)x597.50829 ......\hbox(845.0471+0.0)x597.50829 .......\pdfliteral{ q 1 0 0 1 0 0 cm} .......\hbox(845.0471+0.0)x0.0, glue set - 597.50829fil ........\hbox(845.0471+0.0)x597.50829 .........\pdfrefximage(845.0471+0.0)x597.50829 ........\glue 0.0 plus 1.0fil minus 1.0fil .......\pdfliteral{ Q} ....\penalty 10000 ....\glue(\parfillskip) 0.0 plus 1.0fil ....\glue(\rightskip) 0.0 ...\glue 0.0 ..\glue(\baselineskip) 0.0 ..\hbox(0.0+0.0)x469.75499 <test-include.pdf{psfonts.map} -------------------------------------------- ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2004-08-27 19:23 Message: Logged In: NO Just wanted to confirm that this is solved in MiKTeX's latest release from today (1.20a-rc7.2-2.1). Sorry for the traffic, Robert. (With "expanded fonts are available" I meant that the fonts cmr10+10 etc. exist.) ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2004-08-27 13:18 Message: Logged In: YES user_id=421 This does not crash with the latest teTeX and HEAD pdfTeX. You mention that this does not crash if the expanded fonts are available, but your example uses cm, which obviously _is_ available. And the example works even with an empty map file. This is a MikTeX problem or a bug fixed just recently. ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2004-08-26 23:00 Message: Logged In: NO Sorry, forgot to mention my system: This is pdfeTeX, Version 3.141592-1.20a-rc7.1-2.1 (MiKTeX 2.4) output format initialized to PDF entering extended mode (bugs.tex LaTeX2e <2003/12/01> *File List* minimal.cls 2001/05/25 Standard LaTeX minimal class graphics.sty 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) trig.sty 1999/03/16 v1.09 sin cos tan (DPC) graphics.cfg 2003/03/12 v1.1 MiKTeX 'graphics' configuration pdftex.def 2002/06/19 v0.03k graphics/color for pdftex supp-pdf.tex ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=103&group_id=106

1 0

vadjust.ch
by The Thanh Han 27 Aug '04

27 Aug '04

Hi Martin, now when vadjust is in pdftex, vadjust.ch should be moved under pdftexdir/. Can you please do that? Thanh

3 4

[ pdftex-Bugs-103 ] pdftex crashes when including a file featuring auto expansion
by noreply＠sarovar.org 27 Aug '04

27 Aug '04

Bugs item #103, was opened at 2004-08-26 19:26 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=103&group_id=106 >Category: PDF inclusion >Group: v1.20a >Status: Closed >Resolution: Works For Me Priority: 5 Submitted By: Nobody (None) >Assigned to: Martin Schröder (oneiros) Summary: pdftex crashes when including a file featuring auto expansion Initial Comment: When including a pdf file that contains fonts created with the autoexpand feature, pdftex will crash on the including file. This does not happen if the expanded fonts are available. Neither does it occur with the base 35 fonts (well, I've only tested ptmr8r and phvr8r). Test case below. Regards, Robert. plain tex file to be included (let's call it include.tex): -------------------------------------------- \font\testfont=cmr10\testfont \pdfadjustspacing2 \pdffontexpand\font 20 20 5 autoexpand \hsize=15em Some characters that pretend to make up words which pretend to make sense. \bye -------------------------------------------- latex file on which pdftex crashes: -------------------------------------------- \documentclass{minimal} \usepackage{graphics} \begin{document} \tracingall \includegraphics{include.pdf} \end{document} -------------------------------------------- last lines of the online log (no log file created): -------------------------------------------- Completed box being shipped out [1] \vbox(578.15999+0.0)x469.75499 .\glue 0.0 .\vbox(578.15999+0.0)x469.75499 ..\vbox(0.0+0.0)x469.75499 ...\glue 0.0 plus 1.0fil ...\hbox(0.0+0.0)x469.75499 ..\glue 0.0 ..\glue(\lineskip) 0.0 ..\vbox(578.15999+0.0)x469.75499 ...\glue(\topskip) 0.0 ...\hbox(845.04504+0.0)x469.75499 ....\hbox(0.0+0.0)x20.0 ....\hbox(845.04504+0.0)x597.50682 .....\hbox(845.0471+0.0)x597.50829 ......\hbox(845.0471+0.0)x597.50829 .......\pdfliteral{ q 1 0 0 1 0 0 cm} .......\hbox(845.0471+0.0)x0.0, glue set - 597.50829fil ........\hbox(845.0471+0.0)x597.50829 .........\pdfrefximage(845.0471+0.0)x597.50829 ........\glue 0.0 plus 1.0fil minus 1.0fil .......\pdfliteral{ Q} ....\penalty 10000 ....\glue(\parfillskip) 0.0 plus 1.0fil ....\glue(\rightskip) 0.0 ...\glue 0.0 ..\glue(\baselineskip) 0.0 ..\hbox(0.0+0.0)x469.75499 <test-include.pdf{psfonts.map} -------------------------------------------- ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2004-08-27 09:48 Message: Logged In: YES user_id=421 This does not crash with the latest teTeX and HEAD pdfTeX. You mention that this does not crash if the expanded fonts are available, but your example uses cm, which obviously _is_ available. And the example works even with an empty map file. This is a MikTeX problem or a bug fixed just recently. ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2004-08-26 19:30 Message: Logged In: NO Sorry, forgot to mention my system: This is pdfeTeX, Version 3.141592-1.20a-rc7.1-2.1 (MiKTeX 2.4) output format initialized to PDF entering extended mode (bugs.tex LaTeX2e <2003/12/01> *File List* minimal.cls 2001/05/25 Standard LaTeX minimal class graphics.sty 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) trig.sty 1999/03/16 v1.09 sin cos tan (DPC) graphics.cfg 2003/03/12 v1.1 MiKTeX 'graphics' configuration pdftex.def 2002/06/19 v0.03k graphics/color for pdftex supp-pdf.tex ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=103&group_id=106

1 0

Re: [ pdftex-Bugs-103 ] pdftex crashes when including a file featuring auto expansion
by Akira Kakuto 27 Aug '04

27 Aug '04

> When including a pdf file that contains fonts created > with the autoexpand feature, pdftex will crash on the > including file. It seems ok in Web2C version: This is pdfeTeX, Version 3.141592-1.20a-rc7.2-2.1 (Web2C 7.5.3) output format initialized to PDF entering extended mode Some parts of log file: ... ... ... ... ... ... ........\glue 0.0 plus 1.0fil minus 1.0fil .......\pdfliteral{ Q} ....\penalty 10000 ....\glue(\parfillskip) 0.0 plus 1.0fil ....\glue(\rightskip) 0.0 ...\glue 0.0 ..\glue(\baselineskip) 0.0 ..\hbox(0.0+0.0)x469.75499 <./include.pdf{c:/usr/local/share/texmf/fonts/map/pdftex/updmap/pdftex.map}> Memory usage before: 324&40245; after: 182&40224; still untouched: 1447733 ... ... ... ... ... ... Here is how much of TeX's memory you used: 603 strings out of 95292 7342 string characters out of 1187525 52268 words of memory out of 1500001 3772 multiletter control sequences out of 10000+50000 3640 words of font info for 14 fonts, out of 600000 for 2000 14 hyphenation exceptions out of 2000 18i,4n,17p,192b,92s stack positions out of 1500i,500n,5000p,200000b,5000s 21 PDF objects out of 300000 0 named destinations out of 131072 6 words of extra memory for PDF output out of 300000 Output written on t.pdf (1 page, 18020 bytes). -- Akira Kakuto

1 0

[ pdftex-Bugs-103 ] pdftex crashes when including a file featuring auto expansion
by noreply＠sarovar.org 26 Aug '04

26 Aug '04

Bugs item #103, was opened at 2004-08-26 22:56 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=103&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: pdftex crashes when including a file featuring auto expansion Initial Comment: When including a pdf file that contains fonts created with the autoexpand feature, pdftex will crash on the including file. This does not happen if the expanded fonts are available. Neither does it occur with the base 35 fonts (well, I've only tested ptmr8r and phvr8r). Test case below. Regards, Robert. plain tex file to be included (let's call it include.tex): -------------------------------------------- \font\testfont=cmr10\testfont \pdfadjustspacing2 \pdffontexpand\font 20 20 5 autoexpand \hsize=15em Some characters that pretend to make up words which pretend to make sense. \bye -------------------------------------------- latex file on which pdftex crashes: -------------------------------------------- \documentclass{minimal} \usepackage{graphics} \begin{document} \tracingall \includegraphics{include.pdf} \end{document} -------------------------------------------- last lines of the online log (no log file created): -------------------------------------------- Completed box being shipped out [1] \vbox(578.15999+0.0)x469.75499 .\glue 0.0 .\vbox(578.15999+0.0)x469.75499 ..\vbox(0.0+0.0)x469.75499 ...\glue 0.0 plus 1.0fil ...\hbox(0.0+0.0)x469.75499 ..\glue 0.0 ..\glue(\lineskip) 0.0 ..\vbox(578.15999+0.0)x469.75499 ...\glue(\topskip) 0.0 ...\hbox(845.04504+0.0)x469.75499 ....\hbox(0.0+0.0)x20.0 ....\hbox(845.04504+0.0)x597.50682 .....\hbox(845.0471+0.0)x597.50829 ......\hbox(845.0471+0.0)x597.50829 .......\pdfliteral{ q 1 0 0 1 0 0 cm} .......\hbox(845.0471+0.0)x0.0, glue set - 597.50829fil ........\hbox(845.0471+0.0)x597.50829 .........\pdfrefximage(845.0471+0.0)x597.50829 ........\glue 0.0 plus 1.0fil minus 1.0fil .......\pdfliteral{ Q} ....\penalty 10000 ....\glue(\parfillskip) 0.0 plus 1.0fil ....\glue(\rightskip) 0.0 ...\glue 0.0 ..\glue(\baselineskip) 0.0 ..\hbox(0.0+0.0)x469.75499 <test-include.pdf{psfonts.map} -------------------------------------------- ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2004-08-26 23:00 Message: Logged In: NO Sorry, forgot to mention my system: This is pdfeTeX, Version 3.141592-1.20a-rc7.1-2.1 (MiKTeX 2.4) output format initialized to PDF entering extended mode (bugs.tex LaTeX2e <2003/12/01> *File List* minimal.cls 2001/05/25 Standard LaTeX minimal class graphics.sty 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) trig.sty 1999/03/16 v1.09 sin cos tan (DPC) graphics.cfg 2003/03/12 v1.1 MiKTeX 'graphics' configuration pdftex.def 2002/06/19 v0.03k graphics/color for pdftex supp-pdf.tex ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=103&group_id=106

1 0

[ pdftex-Bugs-102 ] \pdffontexpand without autoexpand produces strange "ligature"
by noreply＠sarovar.org 26 Aug '04

26 Aug '04

Bugs item #102, was opened at 2004-08-20 22:08 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=102&group_id=106 Category: hz Group: v1.20a Status: Open Resolution: None Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: The Thanh Han (hanthethanh) Summary: \pdffontexpand without autoexpand produces strange "ligature" Initial Comment: In the attached test file the fonts are set up by \def\setupfont{ \resetefcode\font \pdffontexpand\font 20 20 5 %autoexpand } This produces a strange "ligature" in the fifth word of the resulting pdf (test/oertzen.pdf): instead of "ä" in "Verhältnis" something quite different is printed. If autoexpand is used, "ä" is printed. Also the log shows control characters at some points in the trace of the first page, most notably in the fonts names (0a and 00). ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2004-08-26 22:57 Message: Logged In: NO I don't think this is a pdftex bug. The virtual font is broken. You get the same result with this plain tex file: ----------------------------------- \font\testfont=pegri9d+20\testfont ä ö ü \char199 \char172 \char185 \char177 \char208 \char174 \char199 \bye ----------------------------------- Running > vftovp pegri9d+20.vf pegri9d+20.tfm test.vp will report some of the broken characters. Regards, Robert. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2004-08-20 22:10 Message: Logged In: YES user_id=421 I tried this with pdfetex and pdftex (not etex), and the effect is the same. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=102&group_id=106

1 0

[ pdftex-Bugs-103 ] pdftex crashes when including a file featuring auto expansion
by noreply＠sarovar.org 26 Aug '04

26 Aug '04

Bugs item #103, was opened at 2004-08-26 22:56 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=103&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: pdftex crashes when including a file featuring auto expansion Initial Comment: When including a pdf file that contains fonts created with the autoexpand feature, pdftex will crash on the including file. This does not happen if the expanded fonts are available. Neither does it occur with the base 35 fonts (well, I've only tested ptmr8r and phvr8r). Test case below. Regards, Robert. plain tex file to be included (let's call it include.tex): -------------------------------------------- \font\testfont=cmr10\testfont \pdfadjustspacing2 \pdffontexpand\font 20 20 5 autoexpand \hsize=15em Some characters that pretend to make up words which pretend to make sense. \bye -------------------------------------------- latex file on which pdftex crashes: -------------------------------------------- \documentclass{minimal} \usepackage{graphics} \begin{document} \tracingall \includegraphics{include.pdf} \end{document} -------------------------------------------- last lines of the online log (no log file created): -------------------------------------------- Completed box being shipped out [1] \vbox(578.15999+0.0)x469.75499 .\glue 0.0 .\vbox(578.15999+0.0)x469.75499 ..\vbox(0.0+0.0)x469.75499 ...\glue 0.0 plus 1.0fil ...\hbox(0.0+0.0)x469.75499 ..\glue 0.0 ..\glue(\lineskip) 0.0 ..\vbox(578.15999+0.0)x469.75499 ...\glue(\topskip) 0.0 ...\hbox(845.04504+0.0)x469.75499 ....\hbox(0.0+0.0)x20.0 ....\hbox(845.04504+0.0)x597.50682 .....\hbox(845.0471+0.0)x597.50829 ......\hbox(845.0471+0.0)x597.50829 .......\pdfliteral{ q 1 0 0 1 0 0 cm} .......\hbox(845.0471+0.0)x0.0, glue set - 597.50829fil ........\hbox(845.0471+0.0)x597.50829 .........\pdfrefximage(845.0471+0.0)x597.50829 ........\glue 0.0 plus 1.0fil minus 1.0fil .......\pdfliteral{ Q} ....\penalty 10000 ....\glue(\parfillskip) 0.0 plus 1.0fil ....\glue(\rightskip) 0.0 ...\glue 0.0 ..\glue(\baselineskip) 0.0 ..\hbox(0.0+0.0)x469.75499 <test-include.pdf{psfonts.map} -------------------------------------------- ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=103&group_id=106

1 0

[ pdftex-Bugs-102 ] \pdffontexpand without autoexpand produces strange "ligature"
by noreply＠sarovar.org 20 Aug '04

20 Aug '04

Bugs item #102, was opened at 2004-08-20 18:38 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=102&group_id=106 Category: hz Group: v1.20a Status: Open Resolution: None Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: The Thanh Han (hanthethanh) >Summary: \pdffontexpand without autoexpand produces strange "ligature" Initial Comment: In the attached test file the fonts are set up by \def\setupfont{ \resetefcode\font \pdffontexpand\font 20 20 5 %autoexpand } This produces a strange "ligature" in the fifth word of the resulting pdf (test/oertzen.pdf): instead of "ä" in "Verhältnis" something quite different is printed. If autoexpand is used, "ä" is printed. Also the log shows control characters at some points in the trace of the first page, most notably in the fonts names (0a and 00). ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2004-08-20 18:40 Message: Logged In: YES user_id=421 I tried this with pdfetex and pdftex (not etex), and the effect is the same. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=102&group_id=106

1 0

[ pdftex-Bugs-102 ] \pdffontexpand without autoexpand produces strange "ligature"
by noreply＠sarovar.org 20 Aug '04

20 Aug '04

Bugs item #102, was opened at 2004-08-20 18:38 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=102&group_id=106 Category: hz Group: v1.20a Status: Open Resolution: None Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: The Thanh Han (hanthethanh) Summary: \pdffontexpand without autoexpand produces strange "ligature" Initial Comment: In the attached test file the fonts are set up by \def\setupfont{ \resetefcode\font \pdffontexpand\font 20 20 5 %autoexpand } This produces a strange "ligature" in the fifth word of the resulting pdf (test/oertzen.pdf): instead of "ä" in "Verhältnis" something quite different is printed. If autoexpand is used, "ä" is printed. Also the log shows control characters at some points in the trace of the first page, most notably in the fonts names (0a and 00). ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=102&group_id=106

1 0

Re: [pdftex] how to crash all (well, some) pdf viewers with pdflatex
by Hans Hagen 18 Aug '04

18 Aug '04

Martin Schröder wrote: >On 2004-07-26 23:52:47 +0200, Hans Hagen wrote: > > >>Acrobat does not like zero transformation matrices; things like >> >> 0.0 0 0 0.0 0 0 cm >> >> > >Which is of course perfectly valid pdf. :-) > > > >>will therefore fail (the wrong operands are 0.0 & 0.0). As far as i know >>this has been reported to adobe. >> >> > >And will be fixed when? :-{ > > don't count on it too much, they probably first want to finish the linxu version 6.0 -) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

3 3

pdftex 1.20a-rc7.1 SlantFont limitcheck
by Hartmut Henkel 16 Aug '04

16 Aug '04

Minor point only: In mapfile.c (e. g. current texlive), somehow the absolute value function for SlantFont range check got lost; the line if ((fm_ptr->slant) >= 1000) { should be: if (abs(fm_ptr->slant) >= 1000) { (The abs() _is_ there for ExtendFont check, so it allows even to type e. g. -1.9 ExtendFont with flipped characters; ok, why not :-) Regards, Hartmut

1 0

feature request
by Hans Hagen 09 Aug '04

09 Aug '04

Hi (challenge for Hartmut -) Is it hard to implement something \pdfximage ... colorspace {...} ... {filename} Where the colorspace spec replaces the one present in the graphic? (in addition, \pdflastximagedepth : 0 = no bitmap, 8, 16, 24, 32 =bitmap) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 2

open problems with 1.20a
by Martin Schröder 31 Jul '04

31 Jul '04

- hz problems. Anything else? Best regards Martin -- Martin Schröder, ms(a)artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de

6 18

Please don't submit unchanged files
by The Thanh Han 27 Jul '04

27 Jul '04

Hi Martin, can you please submit to texlive only files that are changed? It would save me a lot of time browsing those files. When I do a diff, I often get a bunch of files that differ only in their $Id but nothing else. Then it is very difficult to check which files have been changed at all. Thanks, Thanh

2 1

x versus e
by Hans Hagen Outside 24 Jul '04

24 Jul '04

Thanh, The vadjust pre code should be available pdfetex as well, i depend on it ! (ok, we need to fix a border case, but nevertheless, some of my docs produce non optimal output when it's not supported) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

4 7

Schedule 20040721
by Martin Schröder 21 Jul '04

21 Jul '04

We currently have a quite stable version (1.20a-rc7.1). ToDo: - move "vadjust pre" from xtex to etex -> rc7.2 - adopt the patches from peb for etex-pre2.2 -> rc7.3 - update the README for sarovar - fix open problem with hz -> thanh I'll be offline for two weeks starting monday (W31 and W32) and out of office in W33. So I think we should delay the release till W34. Best regards Martin -- Martin Schröder, ms(a)artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de

1 0

\quitvmode patch
by Taco Hoekwater 15 Jul '04

15 Jul '04

Here is another very simple patch. The change file adds a new primitive called \quitvmode. In vertical modes, it is identical to \indent, but in horizontal and math modes it is \noindent. See: http://www.metatex.org/web/quitvmode.html for more information. groeten, Taco

4 6

[ pdftex-Patches-93 ] \quitvmode
by noreply＠sarovar.org 15 Jul '04

15 Jul '04

Patches item #93, was opened at 2004-07-15 12:12 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=93&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: The Thanh Han (hanthethanh) Summary: \quitvmode Initial Comment: The change file adds a new primitive called \quitvmode. In vertical modes, it is identical to \indent, but in horizontal and math modes it is \noindent. See http://www.metatex.org/web/quitvmode.html ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=93&group_id=106

1 0

image inclusion
by Hans Hagen 15 Jul '04

15 Jul '04

Hi Martin, Is there a difference in behavior when with inclusion a boxtype is specified (like not being resused and such?) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 2

Re: backslashes in \pdfoutline
by Hans Hagen 15 Jul '04

15 Jul '04

Heiko Oberdiek wrote: >I think a clear no: > > > it can be done by 'parsing strings' which is painful >If my understanding of Hans's idea is correct then >\escapedpdf can be used the following way, eg. > > \def\foo{bar} > \pdfinfo{/Title (\escapedpdf{\foo})} > > indeed >a) \escapedpdf has to be expandable. >b) The argument is full expanded. >The return value can be a string in the manner of \meaning >(characters with catcode 12 and spaces with catcode 10). > > indeed >b) can be achieved by \edef, but \edef cannot be used >because of a). > >Even if we have a full expanded string, how to parse >it in a safe way? Catcodes? Espacially spaces are >problematic: > > indeed >* \scantokens from e-TeX is AFAIK expandable, but > the catcode changes before are not. > > right, it's also slow to prepare settings (definitions, catcodes etc) actually, it would be handy to have catcode vectors so that we could quickly swap 'm >* For the \@sanitize@onelevel or \meaning method a > macro definition is necessary, violation of a). >* \futurelet is not expandable. >* Scan methods such as \scan#1(... are problematic and fail, > if there are spaces in the string. > > indeed, and * why should we complicate live when it can be programmed (i already wasted too many days on such painful things) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Re: backslashes in \pdfoutline
by Martin Schröder 14 Jul '04

14 Jul '04

On 2004-07-14 10:01:03 -0400, Karl Berry wrote: > I've come to believe that the status should remain quo, and all that's > desirable is to add the warning and fix the sorting. Spending time > implementing autoescape for the benefit of some hypothetical future > macro packages seems like a very low priority feature. Agreed. And even the warning and sorting won't go in 1.20a. Best regards Martin PS: Please let's keep ntg-pdftex at least in the cc. -- Martin Schröder, ms(a)artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de

1 0

Re: backslashes in \pdfoutline
by Hans Hagen 14 Jul '04

14 Jul '04

Karl Berry wrote: > pdftex pipes destinations names through unchanged > >Yes, and many other things as well (having just read through the new >pdftex manual, as Hartmut knows :). Trying to escape all of them seems >more problematic to me now. There are probably more important things >for pdftex development to work on. > > detecting forbidden things: unbalanced unescaped braces and a lonely > backslash at the string end. > > it is dangerous to start adding such features esp since i do some cleanup already far better is to have two primitives \escapedpdf{....} \escapedps{....} \pdfsomething{...... \escapedpdf{....} ...} Hans

1 0

[tex-implementors] MetaTeX project pre-announcement
by Taco Hoekwater 14 Jul '04

14 Jul '04

Hi everybody, I am happy to announce the birth of a new project called MetaTeX. The goal of the MetaTeX project is to create a GPL-ed TeX/MetaPost distribution for POSIX compliant systems, in which the amount of distributed files is minimized while the speed of the TeX 'make' process maximized. This will be done by joining all of the needed functionality into a single executable, and putting all of the texmf input files into a single archive file, eventually resulting in a distribution that (in binary state) will comprise only three actual files: an executable, a data archive, and an options file. As a side-effect, standalone packages of C library-versions of pdfetex, mpost and tex{exec,make} will be created. I am posting this pre- announcement in the hope that people who are interested in this distribution (and, possibly, even want to help) will join our mailing-list. See the website for more information on the project, and how to subscribe. http://www.metatex.org Please do not reply to this message in the group you found it in, since any reply you give will likely be considered off-topic, but feel free to forward this message to people you believe may be interested. Greetings and happy TeX-ing, Taco Hoekwater _______________________________________________ tex-implementors mailing list postmaster(a)tug.org http://tug.org/mailman/listinfo/tex-implementors

1 0

MetaTeX project pre-announcement
by Taco Hoekwater 14 Jul '04

14 Jul '04

Hi everybody, I am happy to announce the birth of a new project called MetaTeX. The goal of the MetaTeX project is to create a GPL-ed TeX/MetaPost distribution for POSIX compliant systems, in which the amount of distributed files is minimized while the speed of the TeX 'make' process maximized. This will be done by joining all of the needed functionality into a single executable, and putting all of the texmf input files into a single archive file, eventually resulting in a distribution that (in binary state) will comprise only three actual files: an executable, a data archive, and an options file. As a side-effect, standalone packages of C library-versions of pdfetex, mpost and tex{exec,make} will be created. I am posting this pre- announcement in the hope that people who are interested in this distribution (and, possibly, even want to help) will join our mailing-list. See the website for more information on the project, and how to subscribe. http://www.metatex.org Please do not reply to this message in the group you found it in, since any reply you give will likely be considered off-topic, but feel free to forward this message to people you believe may be interested. Greetings and happy TeX-ing, Taco Hoekwater

1 0