- ntg-pdftex - NTG Mailing Lists

[ pdftex-Bugs-204 ] pdftex.1.gz: --help has basic info
by noreply＠sarovar.org 27 Sep '04

27 Sep '04

Bugs item #204, was opened at 2004-09-27 17:26 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=204&group_id=106 Category: Documentation Group: None Status: Open Resolution: None Priority: 4 Submitted By: Martin Schröder (oneiros) Assigned to: Hartmut Henkel (hhenkel) Summary: pdftex.1.gz: --help has basic info pdftex.1.gz: --help has basic info that man page lacks Initial Comment: Frank Küster reports things missing in the man page that are in the output of "pdftex --help". See http://www.ntg.nl/pipermail/ntg-pdftex/2004-September/000767.html ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=204&group_id=106

1 0

Re: Bug#273084: pdftex.1.gz: --help has basic info that man page lacks
by Frank Küster 25 Sep '04

25 Sep '04

Hi pdftex team, a user of our Debian package containing pdftex suggested some changes to the man page, along the lines of the text displayed with "pdftex --help". Dan Jacobson <jidanni(a)jidanni.org> wrote: [I pointed him to the sentence that refers the user to the "info file or manual Web2C] > f> The complete documentation for this version of TeX can be found > f> in the info file ... > $ info pdftex > gets the manpage. > > Wait, I see, you should say > > The complete documentation for this version of TeX can be found in the > Info manual Web2C: A TeX implementation. > > or something like that. You see, the "or" between 'info file' and 'manual' could be understand in the sense that there are two files. > f> What wording would you suggest? > > SYNOPSIS should agree with --help: > > pdftex [OPTION]... [TEXNAME[.tex]] [COMMANDS] The TEXNAME[.tex] part is missing currently. Probably it's better to use pdftex [options] [TeX-commands] [texname[.tex] | TeX-commands] to indicate that one can combine TeX-commands at the beginning with an input file. > [or use lower case.] The help message with its uppercase arguments is probably from one of Knuth's files, isn't it? > > Indeed, you could move the pdftex --help section running from > > Run pdfTeX on TEXNAME, usually creating TEXNAME.pdf. > to > If no arguments or options are specified, prompt for input. > > to the man page, because it rather belongs there. Sorry, no patch - I don't understand how pdftex.man is generated from the m4 file. Regards, Frank -- Frank Küster, Biozentrum der Univ. Basel Abt. Biophysikalische Chemie

1 0

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

22 Sep '04

Bugs item #199, was opened at 2004-09-23 02:43 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=199&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody (None) Assigned to: Nobody (None) 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: Nobody (None) Date: 2004-09-23 03:32 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 22 Sep '04

22 Sep '04

Bugs item #199, was opened at 2004-09-23 02:43 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=199&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody (None) Assigned to: Nobody (None) 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. ---------------------------------------------------------------------- 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 19 Sep '04

19 Sep '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-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

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

19 Sep '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-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

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

19 Sep '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-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

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

19 Sep '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-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

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

18 Sep '04

Bugs item #112, was opened at 2004-09-09 10: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

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

18 Sep '04

Bugs item #112, was opened at 2004-09-09 10: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