On Monday 15 April 2013 12:01:16 Graeme Geldenhuys wrote: > On 14/04/13 09:45, Ivanko B wrote: > > Does it mean that the curent state of FPC+MSEgui already provides 100% > > correct handling (input, manipulations, displaying) strings with chars > > above BMP ? > > And if you use the "dreaded UTF-8" [meant as sarcastic], you don't have > to worry about anything, because a UTF-8 implementation automatically > supports the whole Unicode range,
Eh, what about decomposed characters and 1,2,3 or 4 byte code points? > and no worries about Little Endian or > Big Endian (which is also to be considered when using UTF-16). > In process space, really? Please explain. MSEgui does not use utf-16 on disk or over the wire. Martin ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ mseide-msegui-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
