[Fontinst] Re: Bug in fontinstversion{1.927}

[Peter Dyballa]

Hello!

It looks as it could be easy to find all those glyph names that deviate 
from fontinst's naming scheme: the 8p mapping given to ttf2pt1 makes it 
dump an excerpt of the font. Since the map file uses Unicode positions 
the 8p encoded PostScript font contains the glyphs at the right 
positions -- with sometimes different names. The corresponding AFM file 
now has the position (slot number) and the deviating name. With some 
script science it'll be possible to augment both 8p.etx and 8p.mtx 
automatically with Unicode glyph names -- the problem (for me) only is: 
to which Unicode glyphs do the glyphs in OT1, T1, TS1, and expert 
encoding 8j correspond? 8j seems to be no problem since the Adobe Glyph 
List provides a mapping of PostScript glyph names to Unicode slots. But 
these TeX encodings: is there some easy to understand mapping of 
capitalacute, threequartersemdash, hyphendblchar, hyphendbl, 
tieaccentlowercase, newtie ... to Unicode?

Can Dominique Unruh's ucs.sty be useful?

ttf2pt1 has a nice side-effect in augmenting the glyph names' base:

Glyph 1241 name starts with a digit (1661), changing to _b_1241
Glyph 1242 name starts with a digit (1667), changing to _b_1242
Glyph 551 has the same name as 321: (Omega), changing to _d_551
Glyph 554 has the same name as 301: (Delta), changing to _d_554
Glyph 1245 has the same name as 1203: (c6461), changing to _d_1245
Glyph 1247 has the same name as 1205: (c6467), changing to _d_1247

Found with Bitstream CyberBase-Roman. And there are similiar things 
happening in other fonts like Doulos SIL or Code2001 that use numbers 
as glyph names.

--
Greetings

   Pete

"Don't just do something, sit there."