"Mark Malakanov" <markmal_at_rogers.com> wrote in message
news:tfydnfhs-oTUp23fRVn-tw_at_rogers.com...
> Mark Malakanov wrote:
>
>> I wanted to test it but failed to switch windows 2003 to understand 1251
>> codepage :). It should be made via controlpanel, by setting a default
>> language to Russian. I set. And I'm able to type in Russian but when it
>> saves to file it saves ?????????. The same story with SQL*Plus. The oem
>> console and windows eat russian chars. :(
>>
> It was actually a "feature" of SQLPlus (Bug 2858947).
> It can select russian, but it can't insert national chars when database
> codepage is different than national codepage.
> Plus is too smart. It translates from national to main codepage before
> passing to DB. :(
> DB itself can accept and store Russian. for example data can be loaded
> using Loader.
> So, it means that if russian data is stored in NVARCHAR all should be OK.
>
> read also Note:227330.1 Character Sets & Conversion - Frequently Asked
> Questions #14.
Thanks Mark for the info.
It still looks that there is plenty of work to do. (or it must be done a
certain way;)
Received on Wed Aug 03 2005 - 02:33:58 CDT
