February 2005 - ntg-pdftex - NTG Mailing Lists

feature request
by Hans Hagen 08 Feb '05

08 Feb '05

Hi, Some fonts have glyoh variants, e.g. latin modern has umlauts versions and alternative copyright symbols and such. The characteristics of those alternatives don't change, so we could pop them in using an special enc file, which is what i do now. However, in order to fully exploit this feature, we need some extension. Say that we use lmr10 two times, one time with the alternatives, and one time as-is. We need: - two tfm files (the same but a different name) - two mapping lines - one pfb file However, if we have \pdfsetfontenc\somefont{blabla.enc} we can do with - one tfm files (the same but a different name) - one mapping lines (the original) - one pfb file I can even imagine that we have \pdfsetfontfile\somefont{blabla.pfb} \pdfsetfontname\somefont{FunnyFontName} 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 -----------------------------------------------------------------

2 4

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

08 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: Closed >Resolution: Fixed 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 ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-02-08 10:30 Message: Logged In: YES user_id=421 This has been fixed in 1.21a ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=282&group_id=106

1 0

[ pdftex-Bugs-262 ] Type42 inclusion
by noreply＠sarovar.org 08 Feb '05

08 Feb '05

Bugs item #262, was opened at 2005-01-21 10:44 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=262&group_id=106 Category: Fonts Group: v1.20b >Status: Closed >Resolution: Fixed Priority: 3 Submitted By: Nobody (None) Assigned to: Hartmut Henkel (hhenkel) Summary: Type42 inclusion Initial Comment: Hello, Trying to get ttf fonts working both with dvips and pdflatex I experimented with converting the ttf to Type42 using fontforge, disassembling it via t1disasm and creating a pfb with t1asm. The resulting pfb is included via dvips and both ghostscript and distiller can interpret it. Unfortunately, pdflatex gives me the following error trying to include the pfb: Error: pdftex (file FranklinGothic-Medium.pfb): unexpected end of file ==> Fatal error occurred, the output PDF file is not finished! Cheers, Michael ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-02-08 10:30 Message: Logged In: YES user_id=421 This has been fixed in 1.21a ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2005-01-29 23:08 Message: Logged In: YES user_id=929 The attached simple patch for writet1.c checks the /FontType key and if it's 42, pdfTeX exits with an error message: Error: pdfetex (file ./foo.pfb): Type42 fonts unsupported by pdfTeX This could be modified so that an error is given if it's _not_ Type1.But which font types _are_ supported? Another way might be to check the header comment for "%!PS-AdobeFont" or "%!FontType1". But all this can be cheated, and there might be fonts with wrong comment lines floating around... Regards, Hartmut ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-01-27 10:46 Message: Logged In: YES user_id=421 If we decide that Type42 fonts are unsupported, pdftex should at least raise a clear error when it finds them. ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2005-01-27 10:14 Message: Logged In: YES user_id=710 Hi, pdftex doesn't support Type42 fonts and probably won't, unless someone else implements it, as I see little sense in making it work. Thanh ---------------------------------------------------------------------- Comment By: Michael Zedler (zedler) Date: 2005-01-22 14:36 Message: Logged In: YES user_id=2197 Hello, dvips also chokes if it tries to subset the font, including it completely works though. I don't really know if it's worth implementing support for Type42 in pdftex, I wouldn't use it either -- I just tried to find out if dvips+ttf without loss of hinting information is really a no-go as often claimed. Result was: no, no problem ;-) Cheers, Michael ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2005-01-21 23:13 Message: Logged In: YES user_id=929 >From inspection of disassembled font FranklinGothic-Medium.pfb it seems that this Type 42 font is incompatible with writet1.c.Maybe handling Type 42 fonts is not implemented in general? The problem is, that after scanning of the /Encoding array the function t1_subset_ascii_part() is waiting for the string "currentfile eexec" while running the {...} while (t1_in_eexec == 0); loop. But in the Type 42 font there follows the /sfnts key and the Type 42 program is scanned. Then, as t1_in_eexec will never be changed, the while loop runs into the end of the font file, resulting in the error. Looks like it would require quite some change in writet1.c to handle these Type 42 fonts. Would such a change make sense, given that this type of font appears rather seldomly? I also wonder how it should work in dvips, as it uses the same writet1.c, and here also the same error message appears. Also dvipdfm can't process the font, it just hangs. All on teTeX-2.99.9 debian woody i686. Regards, Hartmut ---------------------------------------------------------------------- Comment By: Michael Zedler (zedler) Date: 2005-01-21 15:57 Message: Logged In: YES user_id=2197 You may find the pfb, tfm, vf at http://www.hft.ei.tum.de/mz/test_t42.zip I suppose the error is due to pdftex trying to subset the Type42 font. Cheers, Michael ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-01-21 10:58 Message: Logged In: YES user_id=421 Please include some test files; at least the pfb is needed. Also please login when commenting on this or any other bug. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=262&group_id=106

1 0

1.20c
by Martin Schröder 04 Feb '05

04 Feb '05

Hi, Thomas Esser is close to releasing teTeX 3.00 and asks for a new version of pdftex with all open bugs (!) fixed. Is there anything besides #242 and xpdf 3.00pl3 that should go in? Best regards Martin -- Martin Schröder, ms(a)artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de

5 8

new snapshot
by The Thanh Han 04 Feb '05

04 Feb '05

Hi Martin & Hartmut, I uploaded a new snapshot of pdftex -- this version fixed the problem with ttf embedding and some minor fixes I forgot to apply in the previous version. To Hans: djgpp has also been updated. Thanh

1 0

Re: [NTG-pdftex] .TTF suffix is not supported by kpathsea?
by Akira Kakuto 03 Feb '05

03 Feb '05

> I have been playing with ttf2afm and somehow it cannot open files with > uppercase name (in the current dir). Renaming the file to have lowercase > suffix .ttf helps. Is this the correct behaviour of kpathsea, or I am > doing something wrong? That is the correct behavior. Kpse-allowed suffixes are .ttc and .ttf. -- Akira Kakuto

2 1

strange effect pdfliteral
by Hans Hagen 03 Feb '05

03 Feb '05

Can someone explain why in the last example the pdfliteral messes up the spacing \pdfcompresslevel=0 \setupcolors[state=start] \starttext \def\red #1{\pdfliteral {1 0 0 rg}#1\pdfliteral{0 g}} \def\green#1{\pdfliteral {0 1 0 rg}#1\pdfliteral{0 g}} \def\blue #1{\pdfliteral {0 0 1 rg}#1\pdfliteral{0 g}} \dorecurse{25} {\red{red} \green{green} \blue{blue} } \def\red #1{\pdfliteral direct {1 0 0 rg}#1\pdfliteral{0 g}} \def\green#1{\pdfliteral direct {0 1 0 rg}#1\pdfliteral{0 g}} \def\blue #1{\pdfliteral direct {0 0 1 rg}#1\pdfliteral{0 g}} \dorecurse{25} {\red{red} \green{green} \blue{blue} } \def\red #1{\pdfliteral direct {1 0 0 rg} #1\pdfliteral{0 g}} \def\green#1{\pdfliteral direct {0 1 0 rg} #1\pdfliteral{0 g}} \def\blue #1{\pdfliteral direct {0 0 1 rg} #1\pdfliteral{0 g}} \dorecurse{25} {\red{red} \green{green} \blue{blue} } \def\red #1{\pdfliteral direct {1 0 0 rg}#1\pdfliteral direct {0 g}} \def\green#1{\pdfliteral direct {0 1 0 rg}#1\pdfliteral direct {0 g}} \def\blue #1{\pdfliteral direct {0 0 1 rg}#1\pdfliteral direct {0 g}} \dorecurse{25} {\red{red} \green{green} \blue{blue} } \stoptext ----------------------------------------------------------------- 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 -----------------------------------------------------------------

2 1

.TTF suffix is not supported by kpathsea?
by The Thanh Han 03 Feb '05

03 Feb '05

Hi, I have been playing with ttf2afm and somehow it cannot open files with uppercase name (in the current dir). Renaming the file to have lowercase suffix .ttf helps. Is this the correct behaviour of kpathsea, or I am doing something wrong? Thanh

1 0

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

03 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