October 2004 - ntg-pdftex - NTG Mailing Lists

[ pdftex-Bugs-199 ] font expansion: characters may vanish
by noreply＠sarovar.org 01 Oct '04

01 Oct '04

Bugs item #199, was opened at 2004-09-22 21:13 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=199&group_id=106 Category: hz Group: v1.20a Status: Open Resolution: Accepted Priority: 5 Submitted By: Nobody (None) Assigned to: The Thanh Han (hanthethanh) Summary: font expansion: characters may vanish Initial Comment: For extremely large shrink values, characters may not be visible in the pdf output (although the fonts seem to be embedded), e.g. in the following file: %---------------------------------------------- \hsize220pt \pdfadjustspacing=2 \font\testfont=cmr17 at 90pt\testfont \pdffontexpand\font 0 1000 100 autoexpand \efcode\font`\s=500 \efcode\font`\e=500 \efcode\font`\y=500 see what you get\penalty-10000 \bye %---------------------------------------------- or even worse: %---------------------------------------------- \hsize180pt \pdfadjustspacing=2 \font\testfont=cmr17 at 90pt\testfont \pdffontexpand\font 0 1000 100 autoexpand see what you get\penalty-10000 \bye %---------------------------------------------- The font `cmr17-Extend_100' will not be visible. I only managed to achieve this effect with extremely large font sizes, which may or may not be related (it could also be that I didn't find the `magic' \hsize). If you force the characters to shrink even more, for example by setting \hsize to 120pt in the latter test file, the unexpanded font will be used, thus printing the characters over each other. Regards, Robert <w.m.l(a)gmx.net> PS. I didn't bother to create expanded fonts, so I cannot tell whether it depends on the autoexpand feature. ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2004-10-01 18:41 Message: Logged In: YES user_id=929 tiny patch tries to solve this bug. See README and PDF test file included. Regards, Hartmut ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2004-10-01 15:17 Message: Logged In: YES user_id=421 I you mean the effect in the attached pdf: This is either a bug in Jaws (png attached) or a bug in pdftex. gs 8.30, harlequin 5.3.4a and AR 5 all display the file distorted. :-( ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2004-09-28 22:06 Message: Logged In: NO But the problem I mentioned above in the last paragraph isn't related to Acrobat Reader, is it? % ------------------------------------------ \hsize35pt \pdfadjustspacing=2 \font\testfont=cmr12\testfont \pdffontexpand\font 0 1000 100 autoexpand text text text text\penalty-10000 \bye % ------------------------------------------ Seems like a sanity check is missing somewhere. If my guess is right, pdftex tries to use the font `cmr17-Extend_0', which (incorrectly) translates into the base font. What it should probably do is use the smallest available expanded font, i.e. in this case Extend_100, and make the line overfull. Regards, Robert. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2004-09-27 15:27 Message: Logged In: YES user_id=421 An Acrobat Reader bug. :-) ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2004-09-22 22:02 Message: Logged In: NO Obviously, I filed this report too early. Sorry about that. It is not a pdftex bug, but appears to be a bug in Acrobat Reader 6. (Just to tell you what I saw:) At zoom level 200% or larger, the font most shrunk (Extend_100) is not visible on screen. That is, in the first example, I only see "See y e", in the second, nothing at all. However, if I zoom out, the characters re-appear. Sorry for not zooming out earlier. Regards, Robert. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=199&group_id=106

1 0

[ pdftex-Bugs-199 ] font expansion: characters may vanish
by noreply＠sarovar.org 01 Oct '04

01 Oct '04

Bugs item #199, was opened at 2004-09-22 23:13 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=199&group_id=106 Category: hz Group: v1.20a Status: Open >Resolution: Accepted Priority: 5 Submitted By: Nobody (None) Assigned to: The Thanh Han (hanthethanh) Summary: font expansion: characters may vanish Initial Comment: For extremely large shrink values, characters may not be visible in the pdf output (although the fonts seem to be embedded), e.g. in the following file: %---------------------------------------------- \hsize220pt \pdfadjustspacing=2 \font\testfont=cmr17 at 90pt\testfont \pdffontexpand\font 0 1000 100 autoexpand \efcode\font`\s=500 \efcode\font`\e=500 \efcode\font`\y=500 see what you get\penalty-10000 \bye %---------------------------------------------- or even worse: %---------------------------------------------- \hsize180pt \pdfadjustspacing=2 \font\testfont=cmr17 at 90pt\testfont \pdffontexpand\font 0 1000 100 autoexpand see what you get\penalty-10000 \bye %---------------------------------------------- The font `cmr17-Extend_100' will not be visible. I only managed to achieve this effect with extremely large font sizes, which may or may not be related (it could also be that I didn't find the `magic' \hsize). If you force the characters to shrink even more, for example by setting \hsize to 120pt in the latter test file, the unexpanded font will be used, thus printing the characters over each other. Regards, Robert <w.m.l(a)gmx.net> PS. I didn't bother to create expanded fonts, so I cannot tell whether it depends on the autoexpand feature. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2004-10-01 17:17 Message: Logged In: YES user_id=421 I you mean the effect in the attached pdf: This is either a bug in Jaws (png attached) or a bug in pdftex. gs 8.30, harlequin 5.3.4a and AR 5 all display the file distorted. :-( ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2004-09-29 00:06 Message: Logged In: NO But the problem I mentioned above in the last paragraph isn't related to Acrobat Reader, is it? % ------------------------------------------ \hsize35pt \pdfadjustspacing=2 \font\testfont=cmr12\testfont \pdffontexpand\font 0 1000 100 autoexpand text text text text\penalty-10000 \bye % ------------------------------------------ Seems like a sanity check is missing somewhere. If my guess is right, pdftex tries to use the font `cmr17-Extend_0', which (incorrectly) translates into the base font. What it should probably do is use the smallest available expanded font, i.e. in this case Extend_100, and make the line overfull. Regards, Robert. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2004-09-27 17:27 Message: Logged In: YES user_id=421 An Acrobat Reader bug. :-) ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2004-09-23 00:02 Message: Logged In: NO Obviously, I filed this report too early. Sorry about that. It is not a pdftex bug, but appears to be a bug in Acrobat Reader 6. (Just to tell you what I saw:) At zoom level 200% or larger, the font most shrunk (Extend_100) is not visible on screen. That is, in the first example, I only see "See y e", in the second, nothing at all. However, if I zoom out, the characters re-appear. Sorry for not zooming out earlier. Regards, Robert. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=199&group_id=106

1 0

[ pdftex-Bugs-199 ] font expansion: characters may vanish
by noreply＠sarovar.org 01 Oct '04

01 Oct '04

Bugs item #199, was opened at 2004-09-22 23:13 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=199&group_id=106 >Category: hz >Group: v1.20a >Status: Open Resolution: Rejected Priority: 5 Submitted By: Nobody (None) >Assigned to: The Thanh Han (hanthethanh) Summary: font expansion: characters may vanish Initial Comment: For extremely large shrink values, characters may not be visible in the pdf output (although the fonts seem to be embedded), e.g. in the following file: %---------------------------------------------- \hsize220pt \pdfadjustspacing=2 \font\testfont=cmr17 at 90pt\testfont \pdffontexpand\font 0 1000 100 autoexpand \efcode\font`\s=500 \efcode\font`\e=500 \efcode\font`\y=500 see what you get\penalty-10000 \bye %---------------------------------------------- or even worse: %---------------------------------------------- \hsize180pt \pdfadjustspacing=2 \font\testfont=cmr17 at 90pt\testfont \pdffontexpand\font 0 1000 100 autoexpand see what you get\penalty-10000 \bye %---------------------------------------------- The font `cmr17-Extend_100' will not be visible. I only managed to achieve this effect with extremely large font sizes, which may or may not be related (it could also be that I didn't find the `magic' \hsize). If you force the characters to shrink even more, for example by setting \hsize to 120pt in the latter test file, the unexpanded font will be used, thus printing the characters over each other. Regards, Robert <w.m.l(a)gmx.net> PS. I didn't bother to create expanded fonts, so I cannot tell whether it depends on the autoexpand feature. ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2004-10-01 17:17 Message: Logged In: YES user_id=421 I you mean the effect in the attached pdf: This is either a bug in Jaws (png attached) or a bug in pdftex. gs 8.30, harlequin 5.3.4a and AR 5 all display the file distorted. :-( ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2004-09-29 00:06 Message: Logged In: NO But the problem I mentioned above in the last paragraph isn't related to Acrobat Reader, is it? % ------------------------------------------ \hsize35pt \pdfadjustspacing=2 \font\testfont=cmr12\testfont \pdffontexpand\font 0 1000 100 autoexpand text text text text\penalty-10000 \bye % ------------------------------------------ Seems like a sanity check is missing somewhere. If my guess is right, pdftex tries to use the font `cmr17-Extend_0', which (incorrectly) translates into the base font. What it should probably do is use the smallest available expanded font, i.e. in this case Extend_100, and make the line overfull. Regards, Robert. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2004-09-27 17:27 Message: Logged In: YES user_id=421 An Acrobat Reader bug. :-) ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2004-09-23 00:02 Message: Logged In: NO Obviously, I filed this report too early. Sorry about that. It is not a pdftex bug, but appears to be a bug in Acrobat Reader 6. (Just to tell you what I saw:) At zoom level 200% or larger, the font most shrunk (Extend_100) is not visible on screen. That is, in the first example, I only see "See y e", in the second, nothing at all. However, if I zoom out, the characters re-appear. Sorry for not zooming out earlier. Regards, Robert. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=199&group_id=106

1 0

[ pdftex-Bugs-115 ] character protrusion: some characters will not be protruded
by noreply＠sarovar.org 01 Oct '04

01 Oct '04

Bugs item #115, was opened at 2004-09-10 21:57 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=115&group_id=106 Category: hz Group: v1.20a Status: Open Resolution: None Priority: 5 Submitted By: Nobody (None) Assigned to: The Thanh Han (hanthethanh) Summary: character protrusion: some characters will not be protruded Initial Comment: Some characters will not be protruded into the right margin, namely: `-', `--', and `---', if entered like that. When they occur as \hyphenchar, or as a single character (e.g. \char123), everything's fine. With the EC fonts, the same happens for some quote characters. Here's a plain TeX file showing the problem: ---------------------------------------------------- \tracingoutput 1 \showboxbreadth \maxdimen \showboxdepth \maxdimen \pdfprotrudechars=2 \hsize10em \def\testprotrusion#1{#1\dotfill #1\penalty-10000} \font\testfont=cmr10\testfont \newcount\charcount \charcount=0 \loop \rpcode\font\charcount=1000 \advance\charcount 1 \ifnum\charcount < 256 \repeat \noindent \testprotrusion{A}% OK \testprotrusion{-}% \testprotrusion{--}% \testprotrusion{---}% \testprotrusion{itworks\-likethis}% \testprotrusion{\char123}% \testprotrusion{\char124}% \font\testfont=ecrm10\testfont \charcount=0 \loop \rpcode\font\charcount=1000 \advance\charcount 1 \ifnum\charcount < 256 \repeat \noindent \testprotrusion{``}% \testprotrusion{''}% \testprotrusion{\char13}% \quotedblbase \testprotrusion{\char18}% \quotesinglbase \testprotrusion{Z}% OK \bye ---------------------------------------------------- I don't know whether that might be related, but in all cases, something is being inserted between the character itself and the right margin by TeX (a discretionary for the dashes, a \kern for the quote characters). (This is the same bug as reported in the dctt thread `Randausgleich von Binde- und Trennstrich', 29.8.04) Regards, Robert. ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2004-10-01 14:23 Message: Logged In: YES user_id=929 Hi Robert and Thanh, response on Robert's mail. Please check the test files. Thanh, please comment, help. Thanks a lot! Best Regards Hartmut ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2004-09-28 22:09 Message: Logged In: NO In the README to the patch, you say: > To scroll back over unwanted things I now have extended > the discardable() macro. There was an error in the > original macro anyway, as > > ((type(#) = kern_node) and (subtype(#) <> explicit)) > > is to be discarded, but > > ((type(#) = kern_node) and (subtype(#) = explicit)) > > is not. Does that mean that `\kern1pt A\kern1pt' will not get protruded? And, what about `\kern1pt\unkern A\kern1pt\unkern'? Unfortunately, I'm not able to to test your patch. Could you (or somebody) run this file, and comment on the output, please, or upload the PDF? % ----------------------------------------------------- \pdfprotrudechars=2 \hsize5em \def\testprotrusion#1{#1 \hfill #1\penalty-10000} \font\testfont=cmr10\testfont \lpcode\font`\A=1000 \rpcode\font`\A=1000 \noindent \testprotrusion{A} \testprotrusion{\hskip0ptA\hskip0pt} \testprotrusion{\kern1exA\kern1ex} \testprotrusion{\kern1ex\unkern A\kern1ex\unkern} \testprotrusion{\kern1ex\unkern\kern1ex\unkern A\kern1ex\unkern\kern1ex\unkern} \testprotrusion{\kern1ex\kern1ex\unkern\unkern A\kern1ex\kern1ex\unkern\unkern} \testprotrusion{Z} \bye % ----------------------------------------------------- My concern is about LaTeX packages which might insert kerns as markers. For example, the csquotes package, or the footmisc package. I suppose that protrusion should take place at every point where TeX allows a line break -- is that correct? Regards, Robert ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2004-09-19 23:39 Message: Logged In: YES user_id=929 This patch should solve now the problems with character protrusion, particularily also in combination with font expansion, see the attached PDF files and the README file. Have fun! :-) Hartmut ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2004-09-19 17:09 Message: Logged In: YES user_id=929 still problems with expanded fonts, see PDF ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2004-09-19 13:49 Message: Logged In: YES user_id=929 This patch should work now, see PDF files in the tarball. ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2004-09-19 12:42 Message: Logged In: YES user_id=929 Patch tries to solve the bug. Seems to run with Robert's example. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=115&group_id=106

1 0