> Is there a way to prevent FreeType from synthesizing a Unicode
> charmap, or at least clearly identifying the synthesized charmap as
> such?
Not really.
> In the Python plotting library Matplotlib (of which I am a
> developer), there is an option to use TeX for text rendering; when
> outputting to vector formats the dvi file produced by TeX is then
> parsed (more or less) into a list of (font path, glyph index) pairs,
> where the font path maps to some TeX-supported font (typically
> single-charmap, e.g. pfb) and the glyph index uses that "single"
> charmap. So we then want to get retrieve glyphs according to that
> charmap.
OK.
> In practice, right now we just look up a charmap with either
> TT_ADOBE_ID_STANDARD or TT_ADOBE_ID_CUSTOM encoding, which
> essentially works, but having a way to distinguish the actual
> font-provided charmap from the FreeType-synthesized one seems
> cleaner.
Up to now nobody has asked for such a feature. Can you give a short
outline what you would like FreeType to provide?
Werner
_______________________________________________
Freetype mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype
