I'm using:
PL/SQL Developer
Version 7.1.2.1363
12.41114 - 2 user license
Windows XP Professional 5.1 Build 2600 (Service Pack 2)
and accessing an Oracle 9i database with the following NLS parameters:
Parameter Value
NLS_CALENDAR GREGORIAN
NLS_CHARACTERSET AL32UTF8
NLS_COMP BINARY
NLS_CURRENCY $
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_DUAL_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_LANGUAGE AMERICAN
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_NCHAR_CONV_EXCP FALSE
NLS_NUMERIC_CHARACTERS .,
NLS_RDBMS_VERSION 9.2.0.1.0
NLS_SORT BINARY
NLS_TERRITORY AMERICA
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
On my Windows XP SP2 machine, I have NLS_LANG=AMERICAN_AMERICA.UTF8. When I run PL/SQL Developer and run a query that returns multi-byte characters (Japanese, Chinese, Korean), I get ASCII soup in the output. For example:
COMPANY
(
PL/SQL Developer
Version 7.1.2.1363
12.41114 - 2 user license
Windows XP Professional 5.1 Build 2600 (Service Pack 2)
and accessing an Oracle 9i database with the following NLS parameters:
Parameter Value
NLS_CALENDAR GREGORIAN
NLS_CHARACTERSET AL32UTF8
NLS_COMP BINARY
NLS_CURRENCY $
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_DUAL_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_LANGUAGE AMERICAN
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_NCHAR_CONV_EXCP FALSE
NLS_NUMERIC_CHARACTERS .,
NLS_RDBMS_VERSION 9.2.0.1.0
NLS_SORT BINARY
NLS_TERRITORY AMERICA
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
On my Windows XP SP2 machine, I have NLS_LANG=AMERICAN_AMERICA.UTF8. When I run PL/SQL Developer and run a query that returns multi-byte characters (Japanese, Chinese, Korean), I get ASCII soup in the output. For example:
COMPANY
(