Subject | Transliterate between db and client character sets |
---|---|
Author | Dimitry Sibiryakov |
Post date | 2002-04-23T07:31:58Z |
Hello, All!
Firebird 1.0
I created a field with character set UNICODE_FSS. No proplems here.
Then I connected to the DB using lc_ctype=win1251 and put some
russian data into the field. Still no problems, and I get back my
text in codepage 1251 without errors.
Then I connected to the DB using lc_ctype=cyrl (another russian
character set) and expected to get my data in codepage 866 or
a transliterate error. Nothing like that. I received the same 1251.
That's a trouble, because I have to access to my data from
different platforms (Windows and Linux), which use different codepages
for displaying a text. It is also pity that FB doesn't have
the 'koi8-r' charset.
Is something broken in the internationalisation module?
SY, Dimitry Sibiryakov.
Firebird 1.0
I created a field with character set UNICODE_FSS. No proplems here.
Then I connected to the DB using lc_ctype=win1251 and put some
russian data into the field. Still no problems, and I get back my
text in codepage 1251 without errors.
Then I connected to the DB using lc_ctype=cyrl (another russian
character set) and expected to get my data in codepage 866 or
a transliterate error. Nothing like that. I received the same 1251.
That's a trouble, because I have to access to my data from
different platforms (Windows and Linux), which use different codepages
for displaying a text. It is also pity that FB doesn't have
the 'koi8-r' charset.
Is something broken in the internationalisation module?
SY, Dimitry Sibiryakov.