[Groff] Re: afmtodit problems

[Michail Vidiassov]

Dear Werner,
you wrote:
>> the afmtodit(1) from ver 1.9 told me
>>
>>  If a PostScript character is in the encoding to be used for the
>>  font but is not mentioned in map_file, OR if a generic groff glyph
>>  name can't be deduced using the Adobe Glyph List (built into
>>  afmtodit) then afmtodit will put it in the groff font file as an
>>  unnamed character,
>> we just have to replace "or" with "and".

>I really don't understand this minor difference.  Perhaps you can
>suggest a better wording to make your intentions clear.

I let me present a test case:
test.afm
--------------------------------
StartFontMetrics 4.1
FontName TestFont
ItalicAngle 0
StartCharMetrics 4
C 32 ; WX 250 ; N space ; B 0 0 0 0 ;
C 255 ; WX 500 ; N afii10097 ; B 18 0 461 639 ;
C -1 ; WX 514 ; N afii10194 ; B 16 0 485 799 ;
C -1 ; WX 561 ; N uni044A ; B 20 0 532 639 ;
EndCharMetrics
EndFontMetrics
--------------------------------
command line
-------------------------------
afmtodit.orig test.afm textmap TEST
------------------------------
result (TEST)
-----------------------------
name TEST
internalname TestFont
spacewidth 250
charset
space   250     0       32      space
---     500,639 3       255     afii10097
u0463   514,799 3       256     afii10194
---     561,639 3       257     uni044A
---------------------------------
The second glyph is not encoded in groff, since
 a PostScript character is in the encoding to be used for the
 font but is not mentioned in map_file,
although
 a generic groff glyph name can be deduced using
 the Adobe Glyph List (built into afmtodit),
as it can be seen from the case of the third one,
that was lucky to be unencoded in afm and thus was encoded in groff.

What are the reasons for not encoding the second glyph?

The forth one is broken again, although it is the
simpliest case of the new Abobe glyph naming.


>> BTW, AGL in afmtodit is incomplete, it does not have mappings even
>> for some glyphs from Adobe Cyrillic Encoding (like accents and
>> rarely used cyrillic letters).  Are the problems worth fixing?

>Please send a list.  Are you sure that your glyph names are in

>  http://partners.adobe.com/asn/developer/typeforum/unicodegn.html

0) I was wrong, no need to correct built-in AGL of afmtodit.
1) Are you sure about the URL? May it be
http://partners.adobe.com/asn/tech/type/unicodegn.jsp
2) There are two AGLs now:
aglfn13.txt
# Name:          Adobe Glyph List For New Fonts
# Table version: 1.1
# Date:          17 April 2003
and
glyphlist.txt
# Name:          Adobe Glyph List
# Table version: 2.0
# Date:          September 20, 2002

The difference is PUA, aglfn13.txt does not have any mappings to it.
3) All mappings in my list turned out to be to PUA.
Thus it may be really better to keep them in a separate file, smth.
like adobemap=GGL(from textmap) + AGL PUA mappings(from glyphlist.txt).

            Sincerely, Michail

afmtodit.diff
Description: Text document