Re: FT_Get_Char_Index() returns 0 for char(0x020)

[Tom Kacvinsky]

That was one of the ideas I threw out earlier...

The question is, which formats need to have this kind of sorting done?
CFF/Type 2 fonts require that .notdef have index 0.  What about other
font formats?

On Sun, 15 Oct 2000, Just van Rossum wrote:

> At 5:10 PM +0200 15-10-2000, Werner LEMBERG wrote:
> >> >    2. Define the function as
> >> >
> >> >         FT_Error  FT_Get_Char_Index( FT_Face   face,
> >> >                                      FT_ULong  charcode,
> >> >                                      FT_UInt*  index );
> >> >
> >> > I prefer 2.
> >>
> >> Option 2 sounds fine...
> >
> >David?  Others?  This is an important change, and I want to hear more
> >opinions...
> 
> How about:
> 
>   3.
>   Change the glyph array upon reading the font, to make sure
>   index 0 is always .notdef
> 
> Or am I missing something? The order of the CharStrings dict is completely
> arbitrary, so why not change it? (simply sort it?)
> 
> Just
> 
>