Werner LEMBERG wrote: >> 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).
Perhaps you might add a mention of UTF-32 in the sentence "To convert a Unicode character code to a font glyph index, we use FT_Get_Char_Index, as in" on http://www.freetype.org/freetype2/docs/tutorial/step1.html Best, Adam -- Adam Twardoch | Language Typography Unicode Fonts OpenType | twardoch.com | silesian.com | fontlab.net The illegal we do immediately. The unconstitutional takes a little longer. (Henry Kissinger) _______________________________________________ Freetype mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/freetype
