Helen Borrie wrote:

>>--- In firebird-support@yahoogroups.com, David Johnson wrote:
>>
>>
>>>To store utf-8 or utf-16, you should declare the column with no
>>>character set.
>>>
>>>
>If you want to store unicode characters, declare the columns as
>UNICODE_FSS. If you use character set NONE (or any other single-byte
>character set) the database engine has no way at all to know that each
>character is represented by a 3-byte word.
>
>

But what encoding form does UNICODE_FSS use, or rather what encoding
should I pass to DSQL API functions, UTF-8? That can take up to 6 bytes!
Admittidly most the likely unicode code points fit in 3 bytes, but what
happens when you hit a code that doesn't? Both UTF-16 and 32 also
overflow the 3 byte limit.

Scott