On Mar 31, 2008, at 3:20 PM, Sergey Groznyh wrote:
So my question is, what is the reason for WebKit to treat UTF-16 data as
being little-endian by default?

This is done for compatibility with other browsers (and thus with actual content existing on the Web).

Sounds like you are using native Java support for text decoding. Have you investigated using icu4j? I could turn out to a better match, given that we use ICU in C++, and have quite a few tweaks for Web compatibility in TextCodecICU.

- WBR, Alexey Proskuryakov

_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev

Reply via email to