December 2004 - ntg-pdftex - NTG Mailing Lists

character protrusion with the first letter in a paragraph
by The Thanh Han 19 Jan '05

19 Jan '05

Hi, I have been thinking of the question how to make char protrusion work with the first char of a paragraph. The simplest (and quite robust) solution can be as follows: when considering whether a marginal kern should be inserted, we skip certain kinds of `invisible' node (like adjust node, penalty node and the like). Now to make it work with the first char of a par, we also skip null boxes (box with zero dimen and empty contents) at the left margin. The question is whether such behaviour is ``correct'', and what surprises it can bring in certain situations. Thanh

3 3

Type1, TTF, subsetting, basefont
by Hartmut Henkel 29 Dec '04

29 Dec '04

Hi, there seem to be a few inconsistencies in the way how pdftex handles Type1 vs. TT fonts: 1. Subsetted Type1 fonts get a 6-character with + sign extension like /BaseFont /FCLRSI+CMR10 in the PDF file, but TT fonts don't get this; there it's simply /BaseFont /CMR10 Therefore even subsetted TT fonts are normally _not_ detected as subsetted by the viewer or pdffonts program. So this should probably be added to the TTF routines... 2. For Type1 fonts, the /BaseFont entry is always taken from the /FontName entry in the font. However for TT fonts the /BaseFont entry in the PDF file is copied from the tfmname (!) field in the mapline, if no psname is stated there, else it's taken from the psname of the mapline. E. g. \pdfmapline{+Packa___ <8r.enc <PackardAntique.ttf} gives in the PDF file: /BaseFont /Packa___ (which should be PackardAntique-Regular), whereas \pdfmapline{+Packa___ FOO <8r.enc <PackardAntique.ttf} gives /BaseFont /FOO Here maybe always the /FontName from the TT font should be taken; it's an ASCII string with NameID 6 in the TTF name record. Then it would be consistent with Type1. Regards, Hartmut

4 5

Re: [NTG-context] bookmark & UTF-8 accented characters
by Hans Hagen 27 Dec '04

27 Dec '04

Hi Thanh, In order to get bookmarks to display something else than pdfdoc encoding, we need a fix (extension); we have: \pdfoutline user {...} count ... {text} but also need: \pdfoutline user {...} count ... objrefnr I'll send you a file that shows why -) 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

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

26 Dec '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: Closed >Resolution: Fixed 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 ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2004-12-22 15:53 Message: Logged In: YES user_id=421 This has been fixed in 1.20b ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=112&group_id=106

2 1

[ pdftex-Feature Requests-254 ] fontexpansion, dvi output
by noreply＠sarovar.org 22 Dec '04

22 Dec '04

Feature Requests item #254, was opened at 2004-12-23 02:36 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=254&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: fontexpansion, dvi output Initial Comment: Hello developers, I'd like to use the autoexpand feature with dvips. Are there any plans to make pdftex write the autoexpanded tfm files to the current directory, perhaps even generating a map file? Cheers, Michael ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=254&group_id=106

1 0

Re: [NTG-pdftex] 1.20b/1.21a
by Akira Kakuto 22 Dec '04

22 Dec '04

Martin wrote: > I have problems compiling the latest sources out-of-tree, most > likely because of changes to utils.c: The definition of > ptexbanner has moved. ptexbanner is defined in texmfmp.c. I think you probably did not replace texmfmp.c with the new one. Best regards, Akira

8 27

[ pdftex-Bugs-250 ] writet1.c has problems with HUGE fonts. Patch.
by noreply＠sarovar.org 22 Dec '04

22 Dec '04

Bugs item #250, was opened at 2004-12-11 19:15 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=250&group_id=106 Category: Fonts Group: v1.20a >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Hartmut Henkel (hhenkel) Summary: writet1.c has problems with HUGE fonts. Patch. Initial Comment: Font GoudyIn.pfb causes pdftex segfault, see the README coming with the patch. This tries a fix by dynamic allocation of buffers. As a by-result, PFB and PFA font embedding speed seems to be increased. Needs more testing... ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2004-12-22 15:53 Message: Logged In: YES user_id=421 This has been fixed in 1.20b ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2004-12-12 10:00 Message: Logged In: YES user_id=929 Tried to force re-allocations and made tests with pdftex and dvipsk, see attached .tgz file. Seems to run ok. ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2004-12-11 19:39 Message: Logged In: YES user_id=1608 My version pdfxtex did not exactly segfault, instead it gave the following pdftex_warning(): CharString: invalid access (1) to stack (0 entries) (and gdb showed a somewhat corrupt backtrace, probably both a symptom of the wild pointer). The patch fixed the problem, and I am now looking at a correct PDF document. And I also think it is somewhat faster than before. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=250&group_id=106

1 0

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

22 Dec '04

Bugs item #115, was opened at 2004-09-10 23: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: Closed >Resolution: Fixed 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: Martin Schröder (oneiros) Date: 2004-12-22 15:53 Message: Logged In: YES user_id=421 This has been fixed in 1.20b ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2004-10-01 16: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-29 00: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-20 01: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 19:09 Message: Logged In: YES user_id=929 still problems with expanded fonts, see PDF ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2004-09-19 15: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 14: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-204 ] pdftex.1.gz: --help has basic info that man page lacks
by noreply＠sarovar.org 22 Dec '04

22 Dec '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: Closed >Resolution: Fixed Priority: 4 Submitted By: Martin Schröder (oneiros) Assigned to: Hartmut Henkel (hhenkel) Summary: 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 ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2004-12-22 15:53 Message: Logged In: YES user_id=421 This has been fixed in 1.20b ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=204&group_id=106

1 0

[ pdftex-Bugs-210 ] Map files with many (> 255) different encodings make pdftex segfault. Bug fix by AVL tree.
by noreply＠sarovar.org 22 Dec '04

22 Dec '04

Bugs item #210, was opened at 2004-10-14 02:28 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=210&group_id=106 Category: None Group: v1.20a >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Nobody (None) >Summary: Map files with many (>255) different encodings make pdftex segfault. Bug fix by AVL tree. Initial Comment: See E-Mail describing problem with typesetting chinese texts: Date: Wed, 13 Oct 2004 07:25:41 +0200 From: Lutz Haseloff <Lutz.Haseloff(a)lbapdm.brandenburg.de> Reply-To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> Subject: Re: [NTG-context] Update to Pdfetex 1.20a Hans Hagen schrieb: > Lutz Haseloff wrote: > > > Hi Hans, Hi all, > > > > \loadmapfile[gbk]> > > > > > Is this a bug in pdfetex? > > > welcome to the non downward compatible changes in tex and friends > > \usemodule[chinese] > > \usemodule[chi-simplified] > > \starttext > > \section{test} > > \stoptext Patch seems to be solved by the patch in the attached file. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2004-12-22 15:53 Message: Logged In: YES user_id=421 This has been fixed in 1.20b ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2004-10-14 22:07 Message: Logged In: YES user_id=929 Fixed patch for built-in encodings. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=210&group_id=106

1 0