[Devel] CFF encoding bug (was Type1C encoding weirdness)

[Ivan Nincic]

I did some digging into FT and it seems that CFF encoding structure is not 
properly constructed (cff->encoding.sids & cff->encoding.codes contain 
zeros), on the other hand cff->charset contains a valid array of sids 
(however 'codes' array required for complete encoding specification is not 
present in charset structure).


--------------------------------------------------------------------
Hello,

I have a problem reading encoding information from some Type1 CFF fonts.

The following font has a single CharMap:
 http://www3.telus.net/public/ab114139/type1cff_01.fn

However FT_Get_First_Char/FT_Get_Next_Char/FT_Get_Glyph_Name don't produce
any encoding information. Is this a bug in FreeType?

--
The following font has two encodings (Unicode & adobe_custom)
 http://www3.telus.net/public/ab114139/type1cff_00.fn
When Unicode is selected some characters are misplaced and when custom
encoding is selected FT_Get_First_Char immediately returns glyph index 0
(i.e. no encoding info).

--
Given this behavior I am not certain whether these are FT bugs or there is
some other way (that doesn't depend on driver specific internal structures)
to obtain type1 & cff encoding information.


Ivan

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