> I would recommend to avoid underspecified terminology such as
> "Unicode strings" or "Unicode character codes" in all documentation
> because they only specify the general principle of encoding text but
> don't tell the developer the exact storage format. I recommend to
> replace it with more specific terms such as "Unicode UTF-32 strings"
> or "Unicode UTF-32 character codes" when applicable.
FreeType has no concept for `strings'. You enter a single Unicode
value, and it returns a glyph index. However, I've slightly improved
the documentation of FT_Encoding (which defines possible cmap values).
Werner
_______________________________________________
Freetype mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/freetype
