Re: [Devel] A new CFF encoding bug

[Ivan Nincic]

> > Ok. If the font may not have an encoding is it legal to call
> > FT_Get_First_Char/FT_Get_Next_Char in order to extract glyph names
> > (i.e.  built-in encoding) using FT_Get_Glyph_Name.  This works for
> > the file in question but I wonder if it is generally true for
> > Type1/CFF fonts.
>
> No.  If there is no encoding FT_Get_First_Char/FT_Get_Next_Char can't
> be used -- actually I don't understand how this can work for you with
> `font_buf.cff'.
>
> Instead, you should iterate over all glyph indices
> with FT_Get_Glyph_Name to extract the glyph names so that you can
> build your own encoding.

It works. Give it a try. Although I didn't find a font for which 
FT_Get_First_Char/FT_Get_Next_Char doesn't work, I will switch to a plain 
loop using FT_Get_Glyph_Name.

thanx,

Ivan

_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE* 
http://join.msn.com/?page=features/junkmail