| Subject | Re: [firebird-support] UTF8 database and extended characters in metadata |
|---|---|
| Author | Adriano dos Santos Fernandes |
| Post date | 2008-11-13T11:14:59Z |
Martijn Tonies escreveu:
Because it's not the charset of Windows.
When you type things as ÅÄÖ in Win32 GUI, and sent it as UTF-8, FB is
going to interpret it as an array of bytes in UTF-8. Since first
character has the high bit set to 1, you are telling that this is not 3
characters, but 2 or 1. And it may not be correctly encoded, so the
malformed string error.
Martijn, there may be problem with such types of names, AFAIR some
problem fixed recently may be only fixed in v2.5. If you found new ones,
please tell us, but when using things correct. :-)
One of the problems (even in v2.5) is that you are limited by the number
of bytes (and not characters), so depending on the characters you use
you may be limited by object names of less than 8 characters.
Adriano
>>>And does Database Workbench works in anything other than Windows? :-)
>> Use the correct connection charset for your platform.
>
> Which is? :-)
>
> I was using UTF8...
>
Because it's not the charset of Windows.
When you type things as ÅÄÖ in Win32 GUI, and sent it as UTF-8, FB is
going to interpret it as an array of bytes in UTF-8. Since first
character has the high bit set to 1, you are telling that this is not 3
characters, but 2 or 1. And it may not be correctly encoded, so the
malformed string error.
Martijn, there may be problem with such types of names, AFAIR some
problem fixed recently may be only fixed in v2.5. If you found new ones,
please tell us, but when using things correct. :-)
One of the problems (even in v2.5) is that you are limited by the number
of bytes (and not characters), so depending on the characters you use
you may be limited by object names of less than 8 characters.
Adriano