Re: [Devel] Re-encoding interface requested?

[Tom Kacvinsky]

See the TODO list in a CVS snapshot.  I plan on working on a cmap synthesizer.
I also want to add a a unction like below (though I didn't add it to the list).
What you propose sounds reasonable.  The hooks are there.  YYou pass the glyph
name, find its SID (string ID) and use the SID to find the GID (glyph index)
from the charset table.  The most difficult part of this is the glyph name to
SID mapping, just becuase of how CFF fonts are set up.  In particular, you might
have to iterate over the entire string table in the CFF font to find the SID for
a particular string.  Or you might have to consult the standard strings table

Regards,

Tom

On Mon, 12 Mar 2001, Sander van der Wal wrote:

>
> A couple of weeks ago (8 jan 2001) Leonard Rosenthol had a problem
> with custom encodings for Type 1 fonts and CFF fonts having no cmap.
>
> I have the same problems (because I am also doing a PDF viewer) and I
> think that the solution is to add a function to the public interface
> of freetype2. Right now there's FT_Get_Char_Index, to translate a
> character code to a glyph index. If there would be a function
>
> FT_UInt   FT_Get_Glyphname_Index(FT_Face* face, const FT_String*
> glyph_name)
>
> that returned the glyph index based on the glyph name, client
> applications could do the re-encoding themselves.
>
> Is this a reasonable way? I can work on the implementations.
>