[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Groff] afmtodit problems
From: |
Michail Vidiassov |
Subject: |
[Groff] afmtodit problems |
Date: |
Sat, 4 Oct 2003 12:23:46 +0400 (MSD) |
Dear All,
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,
Why "or"?
If I have a font in a cyrillic encoding, then i have to use a custom
map file, mapping cyrillic glyphs to u???? values, just as afmtodit
does automaticaly for unencoded glyphs. It looks like a useless job.
Custom map files may be desired for something weird, like using
8bit chars in output, but for typical use (GGL from textmap +
AGL from afmtodit) we just have to replace "or" with "and".
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?
Sincerely, Michail
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Groff] afmtodit problems,
Michail Vidiassov <=