Hi, I must have thought of it while implementing the subset tags for type1 fonts. However, to be honest, I don't remember the reason why I left name records of ttf fonts without subset tags (I guess laziness is the correct answer :). Anyway it would be nice to have it fixed. I will download the truetype specification again and look at this issue. Regards, Thanh

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

gives in the PDF file:

/BaseFont /Packa___

(which should be PackardAntique-Regular), whereas

\pdfmapline{+Packa___ FOO <8r.enc

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 _______________________________________________ ntg-pdftex mailing list ntg-pdftex@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-pdftex