> > . If we include a TrueType font as Type 42, it must contain a
> > /CharStrings dictionary which assigns glyph names to all
> > glyphs. With other words, there are always glyph names.
> > Since lilypond builds the Type 42 by itself, it should
> > automatically have access to this data.
>
> How do I get the Unicode codepoints for a TT glyph from freetype?
Use FT_Select_Charmap(face, FT_ENCODING_UNICODE) to select a Unicode
cmap, then loop over all input character codes with
FT_Get_First_Char() and FT_Get_Next_Char(). Those two functions
return the glyph index also.
> In pango-font.cc we only get a glyph index. Also, on windows there
> are further problems with fonts being embedded in duplicate (blowing
> up PDF file sizes) if we embed type42 fonts, which is why the
> windows platform uses GS' loadfontfile routine by default.
Duplicates? I don't understand.
> > . Accessing CID-keyed fonts (this is, fonts which come as PS
> > CIDfont resources, not wrapped as an OTF) is not supported yet,
> > right? It
>
> I guess not, we just make GS read the resource, and hope everything
> works.
The very problem is that a CIDfont resource is useless without a
proper CMap resource. FreeType doesn't (yet) support CMap resources
-- does FontConfig do that?
Werner
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
