On 11/06/2013 11:56 AM, Ivanko B wrote: > Now approx 100% of WWW are utf8, most DB setups are UTF8, most text > editors are UTF8, most LINUX installations are UTF8..
While UTF8 is a perfect code for storing and transport, IMHO it is not at all perfect for being handled by complex software. Here UTF16 is a rather nice compromise (if you in fact need to force a single encoding scheme for text data). As Text I/O (OS-API, file, TCP/IP,... ) usually is done only in very little instances in a major program, conversions at that point do not harm much. As with File and TCP/IP I/O readable Text is only sometimes the data type used, the RTL functions can easily use raw ByteStrings (or just pointers to buffers) and the user might decide which conversion he applies when (s)he accesses such functionality. -Michael ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ mseide-msegui-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
