Helen Borrie wrote:

>At 12:49 PM 10/02/2005 +0000, you wrote:
>
>
>>So if I specify lc_ctype as "UTF-8" I'm safe? (assuming I want to pass
>>UTF-8 form data of course)
>>
>>
>
>No!! the lc_ctype should always match the default character set of the
>database.
>
>

I see, that makes sense.

But I'm still confused about what char encoding I'm supposed to
send/recive via the fbclient.dll API. If it's the local codepage of the
client, then how do you handle a table containing data that doesn't map
to the systems codepage (i.e. a table with english, greek, russian and
korean text).

Windows NT based systems use UTF-16 form text, that is, it doesn't use
the 8-bit char* type the FB API uses for text data but a 16-bit WCHAR*
type, what happens there?

>As for 6-byte characters, you *will* have problems with them if UNICODE_FSS
>can't map them to a 3-byte word it recognises. Which particular 6-byte
>codes did you have in mind?
>
>

The problem is, as far as I can see in the unicode standards there's no
such thing as a FSS encoding of unicode, I can't see anything about a
fixed 3 byte encoding standard. However that's all internal to FB, so
it's not a massive worry so long as it can handle the entire code space
of unicode.

Scott