- ntg-pdftex - NTG Mailing Lists

[ pdftex-Bugs-282 ] TTF embedding
by noreply＠sarovar.org 04 Feb '05

04 Feb '05

Bugs item #282, was opened at 2005-02-04 01:34 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=282&group_id=106 Category: Fonts Group: None Status: Open Resolution: None Priority: 5 Submitted By: Hartmut Henkel (hhenkel) Assigned to: The Thanh Han (hanthethanh) Summary: TTF embedding Initial Comment: pdfeTeX 3.141592-1.20c-beta-20050203-2.2 (Web2C 7.5.4) Some TTF embedding problem, found when i tried the old test files from repaired bug 210. The log tells that chinese font htsong.ttf is embedded.But xpdf-3.0 chokes with Error: Couldn't create a font for 'MWCLGR+SongTi' Error: Couldn't create a font for 'ULNAVB+SongTi' Error: Couldn't create a font for 'FAKOEO+SongTi' and nothing is shown.Previously there were nice chinese characters. See tst.tgz. You also need free htsong.ttf, forgot from where, maybe google after it (it's huge, 9 MB). Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=282&group_id=106

1 0

forgot to apply patch to reject Type42 fonts
by The Thanh Han 03 Feb '05

03 Feb '05

Hi Martin, I forgot to apply the patch from Hartmut to reject Type42 fonts. Can you please apply it then? Thanks. Thanh

2 1

Type3 fonts
by The Thanh Han 03 Feb '05

03 Feb '05

Hi, 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. I was experimenting with it because I wonder whether it makes sense to have mechanism to create user-defined fonts. The answer seems to be no. But anyway, if someone is interested in this issue, please have a look into the pdf I created, maybe I did something wrong. As the files are small so I attached it here, hopefully it doesn't cause any inconvenience. I tried with xpdf, gv and acrobat reader (on linux), and got dots or blank glyph only. In short, it seems that type3 font is not the way to go. Thanh

2 2

re: type 3
by Hans Hagen 03 Feb '05

03 Feb '05

Hi >> inconvenience. I tried with xpdf, gv and acrobat reader (on linux), and >> got dots or blank glyph only. with a bit of merging i can get something produced by metapost visible but only in gsview, changin gyour last part to: \pdfliteral direct {/F2 3009.9626 Tf} AA (i needed a bigger scale -) Is there an example of a file with a type3 that shows up somewhere? 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

[Fwd: Re: [NTG-pdftex] Type3 fonts]
by Hans Hagen 03 Feb '05

03 Feb '05

1 0

pdftex snapshot
by The Thanh Han 02 Feb '05

02 Feb '05

Hi, pdftex-1.20c-beta-20050202 is available at pdftex.sarovar.org/src This snapshot contains all patches from Hartmut and my changes. The djgpp binaries are also available. Thanh

1 0

on the bug "unhbox kills char protrusion"
by The Thanh Han 02 Feb '05

02 Feb '05

Hi, I was scratching my head for a while trying to remember why I wanted do remove margin_kern_node while unboxing. Then I found the following message: ,-------- | Date: Wed, 04 Oct 2000 19:45:49 +0200 | To: Han The Thanh <thanh(a)informatics.muni.cz> | From: Hans Hagen <pragma(a)wxs.nl> | Subject: Re: protruding -- an interesting problem | | At 07:35 PM 10/4/00 +0200, Han The Thanh wrote: | >Hans, | > | >I encoutered an interesting problem of protruding: they are implemented by | >inserting a new kind of node; I named it `margin_kern_node'. A problem | >arose when a paragraph broken into lines is now unboxed; we have some | >extra nodes which cannot be handled by other part of TeX anymore. I | >consider to ignore such nodes when unbox a box. | | Hm. What part? breaking apart boxes are a problem anyway, since marks and | specials interfere. I suggest: | | (1) keep the nodes there when unvboxing | (2) discard them when unhboxing (the lines of such an unvboxed box) | | There's a lot of stuff around that unvboxes, like multi column routines! I | would render your protruding useless. | | | if you have a margin_kern node, then can you also add: \nomarginkern (like | the proposes etex primitive \noligs) which means: don't kern the next char, | | Hans `-------- It is interesting to remove that part as Hartmut did, and see what surprises it can bring :). Thanh

1 0

[ pdftex-Bugs-274 ] \unhbox kills protrusion
by noreply＠sarovar.org 31 Jan '05

31 Jan '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: Open Resolution: None 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: 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

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

31 Jan '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: Open 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-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 31 Jan '05

31 Jan '05

Bugs item #274, was opened at 2005-01-31 02:09 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=274&group_id=106 Category: hz Group: None Status: Open Resolution: None 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> ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=274&group_id=106

1 0