At 8:21 AM +0100 2/14/06, Matthias Buercher wrote:
On 12 févr. 06, at 13:02, Theodore H. Smith wrote:
You can't set a string to have an endian
property. However as Boris correctly mentioned,
binarystreams and memoryblocks can have endian
properties.
not true: there are two variants of utf-16, bigendian and littleendian.
Yet Theo's statement was correct in this case.
You can't, in REALbasic, set a string to be
big-endian or little-endian. UTF-16 text in
REALbasic is always native-endian.
the question remains: how does RB determine the
endianness on an UTF-16 string that does not
have this marker?
It doesn't. It assumes native endianness, even
if it has a BOM (and regardless of its value).
Wrong-endian UTF-16 text is not supported, period.
Best,
- Joe
--
Joseph J. Strout
[EMAIL PROTECTED]
_______________________________________________
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>
