- ntg-pdftex - NTG Mailing Lists

[ pdftex-Bugs-465 ] font expansion & \lastlinefit
by noreply＠sarovar.org 01 Sep '06

01 Sep '06

Bugs item #465, was opened at 2006-01-03 19:05 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=465&group_id=106 Category: hz Group: v1.40.0 Status: Open Resolution: None Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: font expansion & \lastlinefit Initial Comment: With \lastlinefit > 0, the last line will always be expanded to the maximum (except if it doesn't contain a glue). Furthermore, I wonder whether \lastlinefit should ideally also effect the expansion amount (ie., the last line of the first paragraph should be set in cmr10-25, since the preceding one is set in cmr10-50)? \tracingoutput1 \showboxbreadth\maxdimen \pdftracingfonts1 \pdfadjustspacing2 \pdffontexpand\font 50 50 10 autoexpand \lastlinefit500 \hsize=16cm \input tufte\par \bye, Robert ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2006-09-01 11:55 Message: Logged In: YES user_id=710 I should work on it and other bugs related to hz stuff, but I haven't found the time to reread relevant codes yet. Please be patient with me. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-09-01 10:48 Message: Logged In: YES user_id=421 Hartmut? Thanh? Anybody working on this? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=465&group_id=106

1 0

[ pdftex-Bugs-465 ] font expansion & \lastlinefit
by noreply＠sarovar.org 01 Sep '06

01 Sep '06

Bugs item #465, was opened at 2006-01-03 20:05 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=465&group_id=106 Category: hz Group: v1.40.0 Status: Open Resolution: None Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: font expansion & \lastlinefit Initial Comment: With \lastlinefit > 0, the last line will always be expanded to the maximum (except if it doesn't contain a glue). Furthermore, I wonder whether \lastlinefit should ideally also effect the expansion amount (ie., the last line of the first paragraph should be set in cmr10-25, since the preceding one is set in cmr10-50)? \tracingoutput1 \showboxbreadth\maxdimen \pdftracingfonts1 \pdfadjustspacing2 \pdffontexpand\font 50 50 10 autoexpand \lastlinefit500 \hsize=16cm \input tufte\par \bye, Robert ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2006-09-01 12:48 Message: Logged In: YES user_id=421 Hartmut? Thanh? Anybody working on this? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=465&group_id=106

1 0

[ pdftex-Bugs-304 ] Names of expanded fonts not in log output
by noreply＠sarovar.org 01 Sep '06

01 Sep '06

Bugs item #304, was opened at 2005-03-02 18:25 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=304&group_id=106 Category: Fonts Group: v1.21a Status: Open Resolution: Accepted Priority: 5 Submitted By: Robert (schlcht) Assigned to: Hartmut Henkel (hhenkel) Summary: Names of expanded fonts not in log output Initial Comment: When using font expansion, the log output will not contain the names of the expanded fonts but the null character instead (resp. ^^@). %------------------------------------- \pdfadjustspacing=2 \pdffontexpand\font 20 20 5 autoexpand \tracingoutput=1 test \parfillskip 0pt test \bye %------------------------------------- Regards, Robert. ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2006-09-01 12:47 Message: Logged In: YES user_id=421 Is this really a problem, i.e. is there a reason _not_ to use the autoexpand feature in new documents? Hartmut, did you look into this bug? ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2005-10-16 00:24 Message: Logged In: YES user_id=2217 If the font is not autoexpand'ed, its name will still not be written to the log file. (pdftex 1.30.3; same test file, without "autoexpand") Regards, Robert. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-05-12 17:05 Message: Logged In: YES user_id=421 This has been fixed in 1.30.0 ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2005-03-30 22:16 Message: Logged In: YES user_id=929 This patch is based of Thanh's change file showfont.ch, which he gave me during EuroTeX2005 (it's also included, renamed here to showfont-thanh.ch). Use showfont.ch for the patch. There is now a new integer variable \pdftracingfonts. It is zero by default, then we get a log like this (see robert050302.log): ...\tenrm t ...\tenrm (+20) e Without font expansion, this default should be compatible with TeX's original log output. If \pdftracingfonts is set to 1 (or greater), we get a more verbose log (see tst-304.log): ...\xivtt (cmtt10(a)14.0pt) t .\xivtt (cmtt10+20(a)14.0pt) e Seems to work with change file showfont.ch coming directly after after hz.ch. Patch only roughly tested with pdfetex, likely to give problems with pdfxtex, as the variable numbering might differ. Log format to be agreed upon... Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=304&group_id=106

1 0

[ pdftex-Bugs-600 ] \pdfdraftmode: results in segfault + can be tricked
by noreply＠sarovar.org 01 Sep '06

01 Sep '06

Bugs item #600, was opened at 2006-08-23 23:51 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=600&group_id=106 Category: None Group: v1.40.0 >Status: Closed Resolution: Fixed Priority: 5 Submitted By: Robert (schlcht) Assigned to: Martin Schröder (oneiros) Summary: \pdfdraftmode: results in segfault + can be tricked Initial Comment: The following gives a segfault here (under cygwin): \pdfdraftmode=1 \immediate\pdfobj{x} %\pdfoutline goto name{x}{y} % with this, too \pdfcompresslevel=9 A \bye >From the terminal: This is pdfTeXk, Version 3.141592-1.40.0-beta-20060822 (Web2C 7.5.5) %&-line parsing enabled. entering extended mode (./bugs.tex [1{/cygdrive/c/Programme/TeXLive/texmf-var/fonts/map/pdftex/updmap/ pdftex.map} 133 [main] pdftex 1780 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) Segmentation fault (core dumped) Also, the following will create a pdf file, although it shouldn't (or at least issue a warning about \pdfdraftmode being issued too late): \immediate\pdfobj{x} \pdfdraftmode=1 A \bye ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-08-29 23:02 Message: Logged In: YES user_id=421 Updated patch that also gives an error in the case of a late \pdfdraftmode=1 ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-08-29 22:43 Message: Logged In: YES user_id=421 Thanks. The attached patch fixes at least the crash. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=600&group_id=106

1 0

[ pdftex-Bugs-481 ] "This can't happen (flushing)" with extra kerning+expansion+ligatures
by noreply＠sarovar.org 01 Sep '06

01 Sep '06

Bugs item #481, was opened at 2006-02-13 19:04 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=481&group_id=106 Category: hz Group: v1.40.0 Status: Open Resolution: None Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) >Summary: "This can't happen (flushing)" with extra kerning+expansion+ligatures Initial Comment: With the following test file, pdftex will abort with "This can't happen (flushing)": \pdfadjustspacing=1 \pdffontexpand\font 20 20 4 autoexpand \pdfappendkern=1 \knaccode\font`i=100 \hsize10em foo fii foo foo foo foo % but this works: %foo f{}ii foo foo foo foo \bye Hartmut's analysis was: ----------------------------------- FWIW, this happens in function do_subst_font(). But it starts with auto_expand_kern(), where the given kern indeed is appended to the i of "fi" and also to the 2nd "i". It seems as if at this time "fi" is not yet seen as a ligature. Then in do_subst_font() the "fi" is somehow already a ligature, and now the kern is part of the lig_ptr list (which is wrong). Then font(r) is recursively changed to 51, the expanded font number, and so the kern, which should not be in this list, gets the 51 as its type. But it must be 11 for a kern. Maybe a change should be that the kern does not end up in the lig_ptr list, but should come after the "fi" ligature. No idea, how. ----------------------------------- ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2006-09-01 12:43 Message: Logged In: YES user_id=421 Is anybody working on this? ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-02-13 21:25 Message: Logged In: YES user_id=929 My text above had a typo, sorry. Before you start searching... it's auto_append_kern(), not auto_expand_kern(). Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=481&group_id=106

1 0

[ pdftex-Bugs-600 ] \pdfdraftmode: results in segfault + can be tricked
by noreply＠sarovar.org 29 Aug '06

29 Aug '06

Bugs item #600, was opened at 2006-08-23 23:51 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=600&group_id=106 Category: None Group: v1.40.0 Status: Open >Resolution: Fixed Priority: 5 Submitted By: Robert (schlcht) Assigned to: Martin Schröder (oneiros) Summary: \pdfdraftmode: results in segfault + can be tricked Initial Comment: The following gives a segfault here (under cygwin): \pdfdraftmode=1 \immediate\pdfobj{x} %\pdfoutline goto name{x}{y} % with this, too \pdfcompresslevel=9 A \bye >From the terminal: This is pdfTeXk, Version 3.141592-1.40.0-beta-20060822 (Web2C 7.5.5) %&-line parsing enabled. entering extended mode (./bugs.tex [1{/cygdrive/c/Programme/TeXLive/texmf-var/fonts/map/pdftex/updmap/ pdftex.map} 133 [main] pdftex 1780 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) Segmentation fault (core dumped) Also, the following will create a pdf file, although it shouldn't (or at least issue a warning about \pdfdraftmode being issued too late): \immediate\pdfobj{x} \pdfdraftmode=1 A \bye ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2006-08-29 23:02 Message: Logged In: YES user_id=421 Updated patch that also gives an error in the case of a late \pdfdraftmode=1 ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-08-29 22:43 Message: Logged In: YES user_id=421 Thanks. The attached patch fixes at least the crash. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=600&group_id=106

1 0

[ pdftex-Bugs-600 ] \pdfdraftmode: results in segfault + can be tricked
by noreply＠sarovar.org 29 Aug '06

29 Aug '06

Bugs item #600, was opened at 2006-08-23 23:51 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=600&group_id=106 Category: None Group: v1.40.0 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Robert (schlcht) >Assigned to: Martin Schröder (oneiros) Summary: \pdfdraftmode: results in segfault + can be tricked Initial Comment: The following gives a segfault here (under cygwin): \pdfdraftmode=1 \immediate\pdfobj{x} %\pdfoutline goto name{x}{y} % with this, too \pdfcompresslevel=9 A \bye >From the terminal: This is pdfTeXk, Version 3.141592-1.40.0-beta-20060822 (Web2C 7.5.5) %&-line parsing enabled. entering extended mode (./bugs.tex [1{/cygdrive/c/Programme/TeXLive/texmf-var/fonts/map/pdftex/updmap/ pdftex.map} 133 [main] pdftex 1780 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) Segmentation fault (core dumped) Also, the following will create a pdf file, although it shouldn't (or at least issue a warning about \pdfdraftmode being issued too late): \immediate\pdfobj{x} \pdfdraftmode=1 A \bye ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2006-08-29 22:43 Message: Logged In: YES user_id=421 Thanks. The attached patch fixes at least the crash. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=600&group_id=106

1 0

pdfximage
by Hans Hagen 29 Aug '06

29 Aug '06

Hi, It's kind of annoying that pdftex has hard coded suffixes. how about something \pdfjpgsuffixes{jpg,jpeg,myjpg} \pdfpngsuffixes{png,somepng} \pdfpdfsuffixes{pdf,epdf,fdf} 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 8

[ pdftex-Bugs-600 ] \pdfdraftmode: results in segfault + can be tricked
by noreply＠sarovar.org 23 Aug '06

23 Aug '06

Bugs item #600, was opened at 2006-08-23 21:51 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=600&group_id=106 Category: None Group: v1.40.0 Status: Open Resolution: None Priority: 5 Submitted By: Robert (schlcht) Assigned to: Nobody (None) Summary: \pdfdraftmode: results in segfault + can be tricked Initial Comment: The following gives a segfault here (under cygwin): \pdfdraftmode=1 \immediate\pdfobj{x} %\pdfoutline goto name{x}{y} % with this, too \pdfcompresslevel=9 A \bye >From the terminal: This is pdfTeXk, Version 3.141592-1.40.0-beta-20060822 (Web2C 7.5.5) %&-line parsing enabled. entering extended mode (./bugs.tex [1{/cygdrive/c/Programme/TeXLive/texmf-var/fonts/map/pdftex/updmap/ pdftex.map} 133 [main] pdftex 1780 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) Segmentation fault (core dumped) Also, the following will create a pdf file, although it shouldn't (or at least issue a warning about \pdfdraftmode being issued too late): \immediate\pdfobj{x} \pdfdraftmode=1 A \bye ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=600&group_id=106

1 0

1.40.0-beta-20060822
by Martin Schröder 22 Aug '06

22 Aug '06

http://sarovar.org/download.php/1066/pdftex-1.40.0-beta-20060822.tar.bz2 http://sarovar.org/download.php/1067/pdftex-1.40.0-beta-20060811-20060822.d… --------------------------------------------------------------- pdfTeX 3.141592-1.40.0-beta-20060822 was released on 2006-08-22 --------------------------------------------------------------- - new feature: with \pdfdraftmode=1 (or -draftmode) pdfTeX doesn't write an output pdf file and doesn't read the content of any image file, thus speeding up the run. This is usefull when you know you need another run of pdfTeX e.g. just to get all the references right, but don't care for the output of this run - changed the format of pdfTeX warnings and unified the four(!) functions pdfTeX uses for writing out errors and warnings - expanded the output of -version to include information about the libraries used - fixed a bug where -20060811 would loop forever - fixed some compilation problems with obsdcompat Have fun Martin

2 2