September 2004 - ntg-pdftex - NTG Mailing Lists

[ pdftex-Bugs-112 ] Message "output format initialized to" is not always right
by noreply＠sarovar.org 09 Sep '04

09 Sep '04

Bugs item #112, was opened at 2004-09-09 12:13 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=112&group_id=106 Category: None Group: v1.20a Status: Open Resolution: None Priority: 3 Submitted By: Martin Schröder (oneiros) Assigned to: Nobody (None) Summary: Message "output format initialized to" is not always right Initial Comment: The "output format initialized to DVI|PDF" is issued to early, which may lead to confusing results. See the thread "pdftex -ini" at http://www.ntg.nl/pipermail/ntg-pdftex/2004-September/000727.html ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=112&group_id=106

1 0

pdfetex /pdftexbanner gives pdftex
by Hartmut Henkel 09 Sep '04

09 Sep '04

Hi, is it intentional, that in the PDF file the /Producer and /PTEX.Fullbanner keys mention only "...pdfTeX..." even when pdfeTeX is used? And the etex "2.2" does not appear either. Similar with the \pdftexbanner. Regards, Hartmut

3 2

pdftex.sarovar.org
by Martin Schröder 06 Sep '04

06 Sep '04

Hi, this might sound dumb, but how are these files maintained? 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 2

pdftex-1.20a-rc6 is available
by The Thanh Han 06 Sep '04

06 Sep '04

Hi, pdftex-1.20a-rc6 is available (sources + djgpp binaries) at pdftex.sarovar.org this version fixed 2 problems with auto font expansion and margin kerning. If no further problem is found, we expect to release pdftex-1.20a soon Thanh

4 8

pdfetex rc7.2 char protrusion
by Hartmut Henkel 03 Sep '04

03 Sep '04

Has anybody followed this de.comp.text.tex thread? From: Christian Gudrian <usenet(a)gudrian.de> [1] Randausgleich von Binde- und Trennstrich Date: Sun Aug 29 17:23:53 CEST 2004 It deals with a disappearing protrusion at a manually set hyphen dash, e. g. in the test file below the one "Mammut-marsch". \nopagenumbers \pdfprotrudechars=2 \hsize=345pt \rpcode\font`\-=250 \def\sloppy{% \tolerance 9999% \emergencystretch 3em% \hfuzz .5pt \vfuzz\hfuzz} \sloppy Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammut-marsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch Mammutmarsch \end Or is this setup wrong? Only thing i found out is that the particular line with the manual hyphen ends with a disc_node (type 7), but the other lines seem to end with a vlist_node (type 1), whatever that means. And the automatic hyphens have a right_pw of 163840, whereas the manual one has zero there. No clue how to trace this further. Regards, Hartmut

2 1

[ 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