Joseph J. Strout wrote:
Wrong-endian UTF-16 text is not supported, period.
Call it "opposite" endian and we have a deal :-)
It is not "wrong" to have UTF-16 BE strings on a Little Endian
machine, nor vice-versa, nor is it as unusual as one might think.
Sure, it's simple enough to write workaround code, but it should be
built-in (at least marginally correct BOM support). For the
inevitable question/suggestion that follows, the answer is "yes I
have" about 3 years ago, report ID is 'cojoobka'. At least it's been
evaluated :-)
Joshua Hadley
Ascender Corporation | www.ascendercorp.com
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
