Mickey Gabel wrote: >> Is the FreeType API designed to work with UTF-32 directly? If not, how >> does one render non-BMP Unicode character codes? Through UTF-16 >> surrogate pairs? > > AFAIK there are no surrogate pairs in UTF-32, because none are needed. > Unicode code points (20bit) are directly encoded in UTF-32, since there > is enough space, meaning that non-BMP characters can be directly encoded.
Yes, of course. If the FreeType API were based on UTF-16 (like the "wide" variant of the Windows API, for example), then non-BMP characters would need to be accessed through surrogate pairs. But since the FreeType API is based on UTF-32 (I am glad it is), non-BMP characters can be accessed directly. That's good news. A. -- 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 Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype
