7.1. Copy non-English text from any sql-output, Paste it! Result - wrong codepage

[Puxmep]

7.1 Version

Copy non-English text from any SQL-output, then Paste it (in other window for example)!

Result - wrong codepage...

 

[Marco Kalter]

Works fine for me. Can you send me a screenshot that demonstrates it?

 

[Puxmep]

First - select this select "select name from firm"
I see like this
=============
NAME
АБАКАНСКАЯ ТОРГ.БАЗА ТУВИНСКОГО РЕСПОТРЕБСОЮЗА
АБАКАНСКИЙ ЗАВОД "ГАЗСТРОЙДЕТАЛЬ"
АБАКАНСКИЙ ЗАВОД КПД
АБАКАНСКИЙ СТАЛЕЛИТЕЙНЫЙ ЗАВОД
АБАКАНСКИЙ ФИЛИАЛ ОАО "ВОСТОК-СИБПРОМТРАНС"
АБАКАНСКОЕ МОНТАЖНОЕ УПРАВЛЕНИЕ ВОСТОКСАНТЕХМОНТАЖ
АО МАГ СПОРТТОВАРЫ
АО ХАКАССНАБСБЫТ
АОЗТ "ТРИКОТАЖНАЯ ФИРМА ХАКАСИЯ"
АОЗТ ХЛС-САЯНЫ
...
=============

Then copy result in the SQL-Output
then paste... (in SQL-Window)

This is result

 

[CTzen]

It works for me too.

Additional information

SQL> select * from v$nls_parameters where parameter like '%CHARACTERSET';

PARAMETER                    VALUE
-----------------------      -------------
NLS_CHARACTERSET             WE8ISO8859P1
NLS_NCHAR_CHARACTERSET       AL16UTF16

SQL> desc russian_chars
Name Type          Nullable Default Comments
---- ------------- -------- ------- --------
ID   NUMBER        Y
TEXT NVARCHAR2(99) Y

 

[Puxmep]

select * from v$nls_parameters where parameter like '%CHARACTERSET':

My result:

PARAMETER VALUE
NLS_CHARACTERSET CL8MSWIN1251
NLS_NCHAR_CHARACTERSET AL16UTF16

 

[Puxmep]

Hm...
If I switch language to Eglish, then copy Russian text: result is wrong codepage...

But!

If I switch language (before copy) to Russian, then copy Russian text: result is normal codepage!!!

 

[Natalia O.]

I have the same problem.
If I switch the language to German before copying, then the copied and pasted text has an incorrect encoding, but a query with this text retrieves matched rows.
If the current language is Russian, then the text has the right encoding, but the query finds no matches.

Example:

select bezeichnung from verbrauchsarten where bezeichnung = '

 

[Natalia O.]

Is there a workaround for this problem?
We are not able to run queries on our customer's databases from Dev. 7.1.
Please help!!