Re: [Devel] A new CFF encoding bug

[George Williams]

> But if there is no encodind available (i.e. custom encoding) we can't 
> access glyphs by names either ?
No, names are stored seperately from encodings. A font may contain 
glyph names and still not contain an encoding.

> I think that in this case there should be at least a custom encoding 
> (in addition to an optional Unicode encoding). I am right or wrong 
> that a font (Type1, CFF) should always have at least a custom 
> encoding.
If it conforms to Adobe's standards, yes.

> See http://partners.adobe.com/asn/developer/type/unicodegn.html for a 
> detailed algorithm on how to map new glyph names to Unicode.
Sadly Adobe has at least three standard name sets that I'm aware of and 
there are conflicts between at least two of the standards.