February 2005 - ntg-pdftex - NTG Mailing Lists

Type3 fonts and the way to go
by andreas.lobinger＠freenet.de 16 Feb '05

16 Feb '05

Aloha,The Thanh Han posted:>I spent a few hours playing with type3 fonts, but was not able to create>a type3 font that uses another font (type1). It seems that the text>operators somehow doesn't work inside the CharProc stream for type3>fonts.> ...>But anyway, if someone is interested in this issue, please>have a look into the pdf I created, maybe I did something wrong.-Ressources, as Hans Hagen pointed out, the /Ressources of the pageand therefore object 13 need both /Fonts defined. -Encoding, as you're defining chars 97 and 98 and use 'A' and 'B' which are 65 and 66 in my StdEncoding table you won't get that muchpage impression...-Scaling, you need to reread the chapter about text space details. You aredefining a /FontMatrix of [0.001 etc.] which gives you a 1000x1000 glyphcoordinate system. For /A you use this (750 re), but for /B you definea very small /F1. I don't have a facility to compile your f2.tex with an recent pdftex, soi changed the abovementioned points directly in the f2.pdf. Here are the objects with the changes:13 0 obj << /Font << /F2 10 0 R /F1 9 0 R >> /ProcSet [/PDF /Text] >> endobj 10 0 obj << /Type /Font /FontBBox [0 0 1000 1000] /FirstChar 65 /Widths [750 750] /FontMatrix [0.001 0 0 0.001 0 0] /Encoding 5 0 R /CharProcs 4 0 R /Resources 6 0 R /LastChar 66 /Name /F2 /Subtype /Type3 >> endobj 5 0 obj << /Type /Encoding /Differences [65 /A /B] >> endobj 2 0 obj << /Length 35 >> stream 1000 0 d0 BT /F1 900 Tf (B) Tj ET endstream endobj As far as i understand f2.tex it should be very easy to change (except for the /Ressourcesentry). Wishing a happy day LOBI

3 2

[ pdftex-Bugs-292 ] protuding leads to "This can't happen (paragraph)."
by noreply＠sarovar.org 15 Feb '05

15 Feb '05

Bugs item #292, was opened at 2005-02-14 15:22 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=292&group_id=106 Category: hz Group: v1.21a Status: Open Resolution: None Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: Hartmut Henkel (hhenkel) >Summary: protuding leads to "This can't happen (paragraph)." Initial Comment: The input --------------------- \pdfoutput=1 \input edmac \input protcode \font\eightrm=ptmr8t \setprotcode\eightrm \pdfprotrudechars=2 \linenummargin{outer} %% left|right|inner|outer \footparagraph{A} \tracingall\tracingonline=0 \beginnumbering \pstart \text{There}\Afootnote{Habent sua fata libelli. (Der Satz wurde auf Wunsch der Redaktion von »Living Marxism« gestrichen; siehe Korsch an P.~Mattick am 3.10.1938.)}/ is a striking contrast between the impression produced in the minds of West"=European revolutionaries by those short pamphlets of Lenin and Trotsky which appeared in poorly translated and poorly printed editions during the final stage and the aftermath of the war, and the response called forth in Europe and U.S.A. by the belated appearance, in 1927, of the first extra"=Russian versions of Lenin's philosophical work of 1908, on »Materialism and Empirio"=Criticism«. \pend \endnumbering \bye --------------------- (all input files are in the attached archive) leads to --------------------- ! This can't happen (paragraph). <recently read> \par \do@feet ...s \else \Afootstart {A}\Afootgroup {A} \fi \ifvoid \Bfootins \els... \pagecontents ...p \@cclv \unvbox \@cclv \do@feet \ifr@ggedbottom \kern -\di... \pagebody ...\boxmaxdepth \maxdepth \pagecontents } \edmac@output ...e \vbox {\makeheadline \pagebody \makefootline }\fi }\advan... <output> {\edmac@output } ... l.30 \bye I'm broken. Please show this to someone who can fix can fix --------------------- ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2005-02-14 20:42 Message: Logged In: YES user_id=929 Now we know which side effects patch-274 has. When it's reverted, the file is processed without error, but margin kerning is missing (which was the original problem before patch-274). Following experiment is done _with_ patch-274. The "this can't happen" error happens within the line_break routine, which chokes on a margin_kern_node (which was filtered out before patch-274).If one adds margin_kern_node to the do_nothing list, like: mark_node,ins_node,adjust_node,margin_kern_node: do_nothing; othercases confusion("paragraph") it apparently works ok, and margin kerning is fine also (requires patch in hz.ch). But i need to understand how the line_break routine works, whether a do_nothing is the right thing to do... Regards, Hartmut ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-02-14 15:30 Message: Logged In: YES user_id=421 The submitter used the attached edmac.doc; the error is the same. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=292&group_id=106

1 0

[ pdftex-Bugs-292 ] protuding leads to "This can't happen (paragraph)."
by noreply＠sarovar.org 14 Feb '05

14 Feb '05

Bugs item #292, was opened at 2005-02-14 15:22 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=292&group_id=106 Category: hz Group: v1.21a Status: Open Resolution: None Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: Hartmut Henkel (hhenkel) >Summary: protuding leads to "This can't happen (paragraph)." Initial Comment: The input --------------------- \pdfoutput=1 \input edmac \input protcode \font\eightrm=ptmr8t \setprotcode\eightrm \pdfprotrudechars=2 \linenummargin{outer} %% left|right|inner|outer \footparagraph{A} \tracingall\tracingonline=0 \beginnumbering \pstart \text{There}\Afootnote{Habent sua fata libelli. (Der Satz wurde auf Wunsch der Redaktion von »Living Marxism« gestrichen; siehe Korsch an P.~Mattick am 3.10.1938.)}/ is a striking contrast between the impression produced in the minds of West"=European revolutionaries by those short pamphlets of Lenin and Trotsky which appeared in poorly translated and poorly printed editions during the final stage and the aftermath of the war, and the response called forth in Europe and U.S.A. by the belated appearance, in 1927, of the first extra"=Russian versions of Lenin's philosophical work of 1908, on »Materialism and Empirio"=Criticism«. \pend \endnumbering \bye --------------------- (all input files are in the attached archive) leads to --------------------- ! This can't happen (paragraph). <recently read> \par \do@feet ...s \else \Afootstart {A}\Afootgroup {A} \fi \ifvoid \Bfootins \els... \pagecontents ...p \@cclv \unvbox \@cclv \do@feet \ifr@ggedbottom \kern -\di... \pagebody ...\boxmaxdepth \maxdepth \pagecontents } \edmac@output ...e \vbox {\makeheadline \pagebody \makefootline }\fi }\advan... <output> {\edmac@output } ... l.30 \bye I'm broken. Please show this to someone who can fix can fix --------------------- ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2005-02-14 15:30 Message: Logged In: YES user_id=421 The submitter used the attached edmac.doc; the error is the same. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=292&group_id=106

1 0

[ pdftex-Bugs-292 ] protuding leads to "This can't happen (paragraph)."
by noreply＠sarovar.org 14 Feb '05

14 Feb '05

Bugs item #292, was opened at 2005-02-14 15:22 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=292&group_id=106 Category: hz Group: v1.21a Status: Open Resolution: None Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: Hartmut Henkel (hhenkel) Summary: protuding leads to "This can't happen (paragraph)." Initial Comment: The input --------------------- \pdfoutput=1 \input edmac \input protcode \font\eightrm=ptmr8t \setprotcode\eightrm \pdfprotrudechars=2 \linenummargin{outer} %% left|right|inner|outer \footparagraph{A} \tracingall\tracingonline=0 \beginnumbering \pstart \text{There}\Afootnote{Habent sua fata libelli. (Der Satz wurde auf Wunsch der Redaktion von »Living Marxism« gestrichen; siehe Korsch an P.~Mattick am 3.10.1938.)}/ is a striking contrast between the impression produced in the minds of West"=European revolutionaries by those short pamphlets of Lenin and Trotsky which appeared in poorly translated and poorly printed editions during the final stage and the aftermath of the war, and the response called forth in Europe and U.S.A. by the belated appearance, in 1927, of the first extra"=Russian versions of Lenin's philosophical work of 1908, on »Materialism and Empirio"=Criticism«. \pend \endnumbering \bye --------------------- (all input files are in the attached archive) leads to --------------------- ! This can't happen (paragraph). <recently read> \par \do@feet ...s \else \Afootstart {A}\Afootgroup {A} \fi \ifvoid \Bfootins \els... \pagecontents ...p \@cclv \unvbox \@cclv \do@feet \ifr@ggedbottom \kern -\di... \pagebody ...\boxmaxdepth \maxdepth \pagecontents } \edmac@output ...e \vbox {\makeheadline \pagebody \makefootline }\fi }\advan... <output> {\edmac@output } ... l.30 \bye I'm broken. Please show this to someone who can fix can fix --------------------- ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=292&group_id=106

1 0

pdftex1.21a build, linker problem
by andreas.lobinger＠freenet.de 12 Feb '05

12 Feb '05

Aloha, i'm building pdftex on a sort-of standard sparc-sun-solaris2.8. I get a linker problem in building ctangleboot ... /bin/sh ../libtool --mode=link gcc -o ctangleboot ctangleboot.o cwebboot.o lib/lib.a ../kpathsea/libkpathsea.la -lm gcc -o ctangleboot ctangleboot.o cwebboot.o lib/lib.a ../kpathsea/.libs/libkpathsea.a -lm ld: fatal: symbol `main' is multiply-defined: (file ctangleboot.o and file lib/lib.a(main.o)); ld: fatal: File processing errors. No output written to ctangleboot collect2: ld returned 1 exit status gmake: *** [ctangleboot] Error 1 It seems, that the build process is assuming a ld that quietly suppresses multiply defined objects. This shouldn't be so. Wishing a happy day LOBI

4 3

[ pdftex-Patches-257 ] Experimental patch for pdftex character protrusion
by noreply＠sarovar.org 09 Feb '05

09 Feb '05

Patches item #257, was opened at 2005-01-10 21:43 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=257&group_id=106 Category: None Group: Unstable (example) >Status: Closed Resolution: None Priority: 3 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Nobody (None) Summary: Experimental patch for pdftex character protrusion Initial Comment: Normally items inside a \hbox are not considered for protrusion. With this experimental patch also nested \hboxes at the left and right margin are recursively searched for items with \lpcode or \rpcode, and the outmost containing boxes are protruded correspondingly. This seems to be practical e. g. if an elevated \footnote{foo} (LaTeX) index happens to be at the right margin; in this case the footnote index normally is placed too far inward the line. This disturbance was detected by Peter Muthesius in an de.comp.text.tex news thread "pdfcprot und Ziffern am rechten Rand" started Sat Jan 08 14:05:23 CET 2005. Rough experimental patch, rudimentarily tested with left and right protrusion, see test file xx.tex with output xx.pdf. Just for discussion. No warranty. Have fun! Regards, Hartmut ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2005-02-09 20:30 Message: Logged In: YES user_id=929 patch257h has been put into hz.ch for 1.21a (pdftex, pdfetex, pdfxtex) ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2005-01-18 22:19 Message: Logged In: YES user_id=929 Character protrusion patch news: * The protrusion character can now be inside deeply nested \hbox{}, with further (also nested) skipable \hbox{} stuff in the way. The nested list will be recursively searched until a non-skipable item (protrusion character, other character, or list end) is found. * Try to solve left protrusion at paragraph start with \parindent=0pt,by selectively skipping over TeX's empty \hbox{} there. * Protrusion character search by 2 new functions find_protchar_left() and find_protchar_right(), and simple stack. Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=257&group_id=106

1 0

[Fwd: Re: [NTG-pdftex] Type3 fonts and the way to go]
by Hans Hagen 09 Feb '05

09 Feb '05

1 0

[Fwd: Re: [NTG-pdftex] Type3 fonts and the way to go]
by Hans Hagen 09 Feb '05

09 Feb '05

1 0

[ pdftex-Bugs-199 ] font expansion: characters may vanish
by noreply＠sarovar.org 09 Feb '05

09 Feb '05

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: Closed Resolution: Fixed 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: 2005-02-09 12:35 Message: Logged In: YES user_id=421 This has been fixed in 1.21a ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-01-31 13:08 Message: Logged In: YES user_id=421 The state of the patch is indeed fuzzy; at least I did not apply it, but some parts are in. ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2005-01-31 02:59 Message: Logged In: NO It seems as if Hartmut's patch hasn't been applied, as the following test file will still produce incorrect output for both pdftex 1.20b and 1.20c-beta: %------------------------------------------------- \pdfadjustspacing=2 \font\testfont=cmr10 \testfont \pdffontexpand\font 0 1000 100 autoexpand \hsize40pt OK: text text text text\break not OK: text text text text\break \bye %------------------------------------------------- Regards, Robert <w.m.l[at]gmx.net> ---------------------------------------------------------------------- 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 20: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 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-274 ] \unhbox kills protrusion
by noreply＠sarovar.org 09 Feb '05

09 Feb '05

Bugs item #274, was opened at 2005-01-31 03:09 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=274&group_id=106 Category: hz Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: \unhbox kills protrusion Initial Comment: Protrusion will break when boxes containing protruded characters are \unhbox'ed. I've stumbled upon this when using edmac/ledmac, which decomposes each paragraph into lines, then reassembling them. I wasn't sure whether protrusion is supposed to survive this treatment but it does if one uses \unhcopy instead of \unhbox. Here's a greatly reduced example: %-------------------------------------------- \font\testfont=cmr10 \testfont \pdfprotrudechars=2 \rpcode\font`\-=1000 \parindent0pt \hsize=126pt \newbox\testline \newbox\testbox % \setbox\testbox\vbox{% Margin kerning is the adjustments of the characters at the margins of a typeset text. } \loop\ifvbox\testbox \setbox\testline=\vsplit\testbox to\baselineskip \unvbox\testline \setbox\testline=\lastbox \hbox to\hsize{\unhcopy\testline}% OK \hbox to\hsize{\unhbox\testline} % not OK \repeat \bye % -------------------------------------------------- Regards, Robert <w.m.l[at]gmx.net> ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-02-09 12:35 Message: Logged In: YES user_id=421 This has been fixed in 1.21a ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2005-01-31 23:34 Message: Logged In: YES user_id=929 There seems to be one place in hz.ch where \unhbox and \unhcopy are treated differently: %@x [1100] - margin kerning %while link(tail)<>null do tail:=link(tail); %@y %if c = copy_code then begin % while link(tail)<>null do tail:=link(tail); %end %else while link(tail) <> null do begin % r := link(tail); % if not is_char_node(r) and (type(r) = margin_kern_node) then begin % link(tail) := link(r); % free_avail(margin_char(r)); % free_node(r, margin_kern_node_size); % end; % tail:=link(tail); %end; %@z After just commenting this piece out (as shown), both \unhcopy and \unhbox do protrusion ok. Now i don't have the slightest idea what this code is for, neither which side effects would appear if it's removed... Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=274&group_id=106

1 0