[prev in list] [next in list] [prev in thread] [next in thread] 

List:       icu4c-support
Subject:    RE: UTF-32 kroniker delta character to UTF-8 conversion results differ across APIs
From:       "Robert Buck" <rbuck () mathworks ! com>
Date:       2002-10-17 13:30:26
[Download RAW message or body]

I agree to your points.

Okay, so what you are also implying is that, for instance, the
UnicodeString class constructors that take a codepage name, these are
meant for external data, _and_ that data is of the form:

    const uint8_t kronicker_string_utf16[] =
{0xd8,0x35,0xdf,0x39,0x00,0x00};

Rather than of the form:

    UChar kronicker_string_utf16[] = {0xD835,0xDF39,0x0000};


Second, _never_ ever use the following API for UTF-16 streams since it
calls strlen:

UnicodeString::UnicodeString(const char *codepageData, const char
*codepage)

Rather, use the following API:

UnicodeString(const char *codepageData,
        int32_t dataLength,
        const char *codepage = 0);

It might be nice to mention this in the API doc.

Bob

_______________________________________________
icu4c-support@oss.software.ibm.com - icu4c-support mailing list
To Un/Subscribe:
http://oss.software.ibm.com/developerworks/oss/mailman/listinfo/icu4c-support
[prev in list] [next in list] [prev in thread] [next in thread]