Displaying multiple asian character sets?

Hi all,
Just wondering is there anyway to display multiple asian keysets in a java application?
Right now I can set the locale to say Chinese with the command line property:
-Duser.language=zh
I could do the same with Japanese or Korean. But I was wondering is there anyway to display all these character sets in the same program? Would I have to set the JTextFields individually to the relevant fonts so i can see the characters? E.g. if the user wants to input Chinese, all JTextFields are set to Simsun. Same for other character sets?
thanks,
J

Hi Justin,
As for myself, I used Robot class on Win Xp to switch between input languages in a form (French/Japanese). That works well but requires that you map manually each language to a key combination a Robot can emule.
I hope that could be useful,
Best regards,
Lionel Badiou
CodeFutures -
Java Code Generation
http://www.codefutures.com

Similar Messages

Displaying multiple asian key sets?

Hi all,
Just wondering is there anyway to display multiple asian keysets in a java application?
Right now I can set the locale to say Chinese with the command line property:
-Duser.language=zh
I could do the same with Japanese or Korean. But I was wondering is there anyway to display all these character sets in the same program? Would I have to set the JTextFields individually to the relevant fonts so i can see the characters? E.g. if the user wants to input Chinese, all JTextFields are set to Simsun. Same for other character sets?
thanks,
J

1) Provide a font that has all such character sets (Korean, Japanese, Traditional Chinese and Simplified Chinese) -
2) Recognize the different ranges, and display the text of different languages with different fonts - for instance, using Gulim for Korean, MingLiu for Chinese, Mincho for Japanese - not an easy task. (For instance, the Kanji - chinese characters used in Japanese, and Hanja - chinese characters used in Korean, could be depicted using the MingLiu font, but there's some characters from Kanji and Hanja that are missing in MingLiu). Such recognizing is done by some modern browsers, like IE and Mozilla. (You can write a 3-language page using UTF-8 encoding and all the characters will be correctly shown)

[SOLVED] Browser cannot display the full character set

Characters from some languages like persian, vietnames, japanese, chinese are not displayed in my browsers (I have chromium and firefox installed). The browser just displays little squares. However I don't think it is a problem with the browser but the x installation. I think I have all basic fonts installed.
In my x-installation I have the following fonts installed (These are all fonts I could find via 'pacman -Ss xorg-font').
extra/font-misc-ethiopic 1.0.3-1 (xorg xorg-fonts) [installed]
X.org Misc Ethiopic fonts
extra/xorg-font-util 1.3.0-2 (xorg-fonts xorg) [installed]
X.Org font utilities
extra/xorg-font-utils 7.6-4 [installed]
Transitional package depending on xorg font utilities
extra/xorg-fonts-100dpi 1.0.1-5 (xorg) [installed]
X.org 100dpi fonts
extra/xorg-fonts-75dpi 1.0.3-1 (xorg) [installed]
X.org 75dpi fonts
extra/xorg-fonts-alias 1.0.3-1 [installed]
X.org font alias files
extra/xorg-fonts-cyrillic 1.0.1-4
X.org cyrillic fonts
extra/xorg-fonts-encodings 1.0.4-4 (xorg-fonts xorg) [installed]
X.org font encoding files
extra/xorg-fonts-misc 1.0.1-3 [installed]
X.org misc fonts
extra/xorg-fonts-type1 7.4-3 [installed]
X.org Type1 fonts
Can anybody give me a hint on how to diagnose the problem.
Last edited by helmut (2014-07-10 15:29:41)

Read the wiki article on CJKV fonts: https://wiki.archlinux.org/index.php/Fo … Vietnamese
Last edited by karol (2014-07-10 15:09:16)

Lync in combination with Plantronics P540-M: Display changes to logographic character set

Hello,
I've recently started to use Lync on my iMac 21,5" from 2011. Now the program itself works fine until i connect a Plantronics P540-M usb phone. Lynn keeps operating as it should apart from the fact that
the display on the Plantronics phone changes to some sort of asian character set. I'm using Lync version 14.0.10.
Does anyone recognise this problem and have a solution for this?
With kind regards,
Patrick van Kleeff
Windesheim University of Applied Sciences

Language is passed to phone from Lync.
Try this:
Go to System Preferences – Available from the Apple menu.
Click on Language & Region – It is the flag icon in the top row of icons.
Make sure English is the primary language. If another language is listed, remove it.
Reboot
Launch Lync
If that does not work try this:
Change the language from "English-Primary" to "English-US"
Reboot
Go back into Settings, Language & Region
Change the language back to "English-Primary"
Reboot
Launch Lync

US7ASCII character set Please Suggest ???

Dear all,
Does US7ASCII have support for asian character set.
Oracle 9.2.0.7, Solaris 10
Thanks in advance
SL
Connected to: Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses WE8ISO8859P1 character set (possible charset conversion)
Message was edited by:
user480060
I know the answer. US7ascii is 7 bit. Now my question is that how do I convert this to another character set (8 bit) PLease help
Message was edited by:
user480060
ALTER DATABASE [<db_name>] CHARACTER SET <new_character_set>;
Will this be enough to change the existing character set. At this moment the database is empty. Will there be no issues later on.???
Message was edited by:
user480060

Which will be the new character set ?
If the new character set is a binary superset of the old character set, you can use the following procedure:
http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96529/ch10.htm#1009904
Following table lists all US7ASCII supersets:
http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96529/appa.htm#974388

Checking server character set

I think this is a simple question, but for some reason I am not able to find the result.
How can I check the server's default character set?
We have HP-UX (unix) servers, and most databases are set to AL32UTF8/AL16UTF16.
I thought it would be something simple like typing 'locale', but on the HP-UX box(es), it doesn't show any setting for LANG.
I also executed 'env' and looked at all settings, but nothing seems relevant.
Unless I explicitly set the NLS_LANG=AMERICAN_AMERICA.AL32UTF8, when I do an export, it shows:
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses AL32UTF8 character set (possible charset conversion)
Where is it getting the US7ASCII?
If I select * from nls_database_parameters; there is no setting like US7ASCII.
When I do a 'man -k character', I get numerous possible commands, but none of them appear to be something that displays the default character set.
But, as I noted above, when I run an export of our database (without setting the NLS_LANG), it shows me that the default character set is US7ASCII.
So, how do I show this, and if you might also have any ideas how to change this to UTF8.
Thanks.
removed references in this posting to my linux boxes...

The default O/S character set for Unix is 7-bit ASCII. This is element of so-called "C locale". This locale is used by all applications that do not declare themselves sensitive to user locale (i.e. they do not call setlocale() at application startup) and by all applications that have no locale parameters (LANG, or LC_xxxx) set in their environment.
If you call 'locale' in a Unix session that has no locale environment set, the "C locale" should be reported.
"C locale" uses US locale formatting conventions and binary collation.
## "Export done in US7ASCII character set and AL16UTF16 NCHAR character set
## server uses AL32UTF8 character set (possible charset conversion)"
Here, US7ASCII is the default character set of an Oracle Client. It is not directly related to the default O/S character set. US7ASCII is always the default Oracle client character set on all non-EBCDIC platforms, used if NLS_LANG is not explicitly set.
-- Sergiusz

Change character set

Hi
is anyone can tell me how to change characterset.
i try with alter session but it doesnt work.
thanks

Article from Metalink
Doc ID: Note:66320.1
Subject: Changing the Database Character Set or the Database National Character Set
Type: BULLETIN
Status: PUBLISHED
 Content Type: TEXT/PLAIN
Creation Date: 23-OCT-1998
Last Revision Date: 12-DEC-2003
PURPOSE ======= To explain how to change the database character set or national character set of an existing Oracle8(i) or Oracle9i database without having to recreate the database. 1. SCOPE & APPLICATION ====================== The method described here is documented in the Oracle 8.1.x and Oracle9i documentation. It is not documented but it can be used in version 8.0.x. It does not work in Oracle7. The database character set is the character set of CHAR, VARCHAR2, LONG, and CLOB data stored in the database columns, and of SQL and PL/SQL text stored in the Data Dictionary. The national character set is the character set of NCHAR, NVARCHAR2, and NCLOB data. In certain database configurations the CLOB and NCLOB data are stored in the fixed-width Unicode encoding UCS-2. If you are using CLOB or NCLOB please make sure you read section "4. HANDLING CLOB AND NCLOB COLUMNS" below in this document. Before changing the character set of a database make sure you understand how Oracle deals with character sets. Before proceeding please refer to [NOTE:158577.1] "NLS_LANG Explained (How Does Client-Server Character Conversion Work?)". See also [NOTE:225912.1] "Changing the Database Character Set - an Overview" for general discussion about various methods of migration to a different database character set. If you are migrating an Oracle Applications instance, read [NOTE:124721.1] "Migrating an Applications Installation to a New Character Set" for specific steps that have to be performed. If you are migrating from 8.x to 9.x please have a look at [NOTE:140014.1] "ALERT: Oracle8/8i to Oracle9i Using New "AL16UTF16"" and other referenced notes below. Before using the method described in this note it is essential to do a full backup of the database and to use the Character Set Scanner utility to check your data. See the section "2. USING THE CHARACTER SET SCANNER" below. Note that changing the database or the national character set as described in this document does not change the actual character codes, it only changes the character set declaration. If you want to convert the contents of the database (character codes) from one character set to another you must use the Oracle Export and Import utilities. This is needed, for example, if the source character set is not a binary subset of the target character set, i.e. if a character exists in the source and in the target character set but not with the same binary code. All binary subset-superset relationships between characters sets recognized by the Oracle Server are listed in [NOTE:119164.1] "Changing Database Character Set - Valid Superset Definitions". Note: The varying width character sets (like UTF8) are not supported as national character sets in Oracle8(i) (see [NOTE:62107.1]). Thus, changing the national character set from a fixed width character set to a varying width character set is not supported in Oracle8(i). NCHAR types in Oracle8 and Oracle8i were designed to support special Oracle specific fixed-width Asian character sets, that were introduced to provide higher performance processing of Asian character data. Examples of these character sets are : JA16EUCFIXED ,JA16SJISFIXED , ZHT32EUCFIXED. For a definition of varying width character sets see also section "4. HANDLING CLOB AND NCLOB COLUMNS" below. WARNING: Do not use any undocumented Oracle7 method to change the database character set of an Oracle8(i) or Oracle9i database. This will corrupt the database. 2. USING THE CHARACTER SET SCANNER ================================== Character data in the Oracle 8.1.6 and later database versions can be efficiently checked for possible character set migration problems with help of the Character Set Scanner utility. This utility is included in the Oracle Server 8.1.7 software distribution and the newest Character Set Scanner version can be downloaded from the Oracle Technology Network site, http://otn.oracle.com The Character Set Scanner on OTN is available for limited number of platforms only but it can be used with databases on other platforms in the client/server configuration -- as long as the database version matches the Character Set Scanner version and platforms are either both ASCII-based or both EBCDIC-based. It is recommended to use the newest Character Set Scanner version available from the OTN site. The Character Set Scanner is documented in the following manuals: - "Oracle8i Documentation Addendum, Release 3 (8.1.7)", Chapter 3 - "Oracle9i Globalization Support Guide, Release 1 (9.0.1)", Chapter 10 - "Oracle9i Database Globalization Support Guide, Release 2 (9.2)", Chapter 11 Note: The Character Set Scanner coming with Oracle 8.1.7 and Oracle 9.0.1 does not have a separate version number. It reports the database release number in its banner. This version of the Scanner does not check for illegal character codes in a database if the FROMCHAR and TOCHAR (or FROMNCHAR and TONCHAR) parameters have the same value (i.e. you simulate migration from a character set to itself). The Character Set Scanner 1.0, available on OTN, reports its version number as x.x.x.1.0, where x.x.x is the database version number. This version adds a few bug fixes and it supports FROMCHAR=TOCHAR provided it is not UTF8. The Character Set Scanner 1.1, available on OTN and with Release 2 (9.2) of the Oracle Server, reports its version number as v1.1 followed by the database version number. This version adds another bug fixes and the full support for FROMCHAR=TOCHAR. None of the above versions of the Scanner can correctly analyze CLOB or NCLOB values if the database or the national character set, respectively, is multibyte. The Scanner reports such values randomly as Convertible or Lossy. The version 1.2 of the Scanner will mark all such values as Changeless (as they are always stored in the Unicode UCS-2 encoding and thus they do not change when the database or national character set is changed from one multibyte to another). Character Set Scanner 2.0 will correctly check CLOBs and NCLOBs for possible data loss when migrating from a multibyte character set to its subset. To verify that your database contains only valid codes, specify the new database character set in the TOCHAR parameter and/or the new national character set in the TONCHAR parameter. Specify FULL=Y to scan the whole database. Set ARRAY and PROCESS parameters depending on your system's resources to speed up the scanning. FROMCHAR and FROMNCHAR will default to the original database and national character sets. The Character Set Scanner should report only Changless data in both the Data Dictionary and in application data. If any Convertible or Exceptional data are reported, the ALTER DATABASE [NATIONAL] CHARACTER SET statement must not be used without further investigation of the source and type of these data. In situations in which the ALTER DATABASE [NATIONAL] CHARACTER SET statement is used to repair an incorrect database character set declaration rather than to simply migrate to a new wider character set, you may be advised by Oracle Support Services analysts to execute the statement even if Exceptional data are reported. For more information see also [NOTE:225912.1] "Changing the Database Character Set - a short Overview". 3. CHANGING THE DATABASE OR THE NATIONAL CHARACTER SET ====================================================== Oracle8(i) introduces a new documented method of changing the database and national character sets. The method uses two SQL statements, which are described in the Oracle8i National Language Support Guide: ALTER DATABASE [<db_name>] CHARACTER SET <new_character_set> ALTER DATABASE [<db_name>] NATIONAL CHARACTER SET <new_NCHAR_character_set> The database name is optional. The character set name should be specified without quotes, for example: ALTER DATABASE CHARACTER SET WE8ISO8859P1 To change the database character set perform the following steps. Note that some of them have been erroneously omitted from the Oracle8i documentation: 1. Use the Character Set Scanner utility to verify that your database contains only valid character codes -- see "2. USING THE CHARACTER SET SCANNER" above. 2. If necessary, prepare CLOB columns for the character set change -- see "4. HANDLING CLOB AND NCLOB COLUMNS" below. Omitting this step can lead to corrupted CLOB/NCLOB values in the database. If SYS.METASTYLESHEET (STYLESHEET) is populated (9i and up only) then see [NOTE:213015.1] "SYS.METASTYLESHEET marked as having convertible data (ORA-12716 when trying to convert character set)" for the actions that need to be taken. 3. Make sure the parallel_server parameter in INIT.ORA is set to false or it is not set at all. 4. Execute the following commands in Server Manager (Oracle8) or sqlplus (Oracle9), connected as INTERNAL or "/ AS SYSDBA": SHUTDOWN IMMEDIATE; -- or NORMAL <do a full database backup> STARTUP MOUNT; ALTER SYSTEM ENABLE RESTRICTED SESSION; ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0; ALTER SYSTEM SET AQ_TM_PROCESSES=0; ALTER DATABASE OPEN; ALTER DATABASE CHARACTER SET <new_character_set>; SHUTDOWN IMMEDIATE; -- OR NORMAL STARTUP RESTRICT; 5. Restore the parallel_server parameter in INIT.ORA, if necessary. 6. Execute the following commands: SHUTDOWN IMMEDIATE; -- OR NORMAL STARTUP; The double restart is necessary in Oracle8(i) because of a SGA initialization bug, fixed in Oracle9i. 7. If necessary, restore CLOB columns -- see "4. HANDLING CLOB AND NCLOB COLUMNS" below. To change the national character set replace the ALTER DATABASE CHARACTER SET statement with ALTER DATABASE NATIONAL CHARACTER SET. You can issue both statements together if you wish. Error Conditions ---------------- A number of error conditions may be reported when trying to change the database or national character set. In Oracle8(i) the ALTER DATABASE [NATIONAL] CHARACTER SET statement will return: ORA-01679: database must be mounted EXCLUSIVE and not open to activate - if you do not enable restricted session - if you startup the instance in PARALLEL/SHARED mode - if you do not set the number of queue processes to 0 - if you do not set the number of AQ time manager processes to 0 - if anybody is logged in apart from you. This error message is misleading. The command requires the database to be open but only one session, the one executing the command, is allowed. For the above error conditions Oracle9i will report one of the errors: ORA-12719: operation requires database is in RESTRICTED mode ORA-12720: operation requires database is in EXCLUSIVE mode ORA-12721: operation cannot execute when other sessions are active Oracle9i can also report: ORA-12718: operation requires connection as SYS if you are not connect as SYS (INTERNAL, "/ AS SYSDBA"). If the specified new character set name is not recognized, Oracle will report one of the errors: ORA-24329: invalid character set identifier ORA-12714: invalid national character set specified ORA-12715: invalid character set specified The ALTER DATABASE [NATIONAL] CHARACTER SET command will only work if the old character set is considered a binary subset of the new character set. Oracle Server 8.0.3 to 8.1.5 recognizes US7ASCII as the binary subset of all ASCII-based character sets. It also treats each character set as a binary subset of itself. No other combinations are recognized. Newer Oracle Server versions recognize additional subset/superset combinations, which are listed in [NOTE:119164.1]. If the old character set is not recognized as a binary subset of the new character set, the ALTER DATABASE [NATIONAL] CHARACTER SET statement will return: - in Oracle 8.1.5 and above: ORA-12712: new character set must be a superset of old character set - in Oracle 8.0.5 and 8.0.6: ORA-12710: new character set must be a superset of old character set - in Oracle 8.0.3 and 8.0.4: ORA-24329: invalid character set identifier You will also get these errors if you try to change the characterset of a US7ASCII database that was started without a (correct) ORA_NLSxx parameter. See [NOTE:77442.1] It may be necessary to switch off the superset check to allow changes between formally incompatible character sets to solve certain character set problems or to speed up migration of huge databases. Oracle Support Services may pass the necessary information to customers after verifying the safety of the change for the customers' environments. If in Oracle9i an ALTER DATABASE NATIONAL CHARACTER SET is issued and there are N-type colums who contain data then this error is returned: ORA-12717:Cannot ALTER DATABASE NATIONAL CHARACTER SET when NCLOB data exists The error only speaks about Nclob but Nchar and Nvarchar2 are also checked see [NOTE:2310895.9] for bug [BUG:2310895] 4. HANDLING CLOB AND NCLOB COLUMNS ================================== Background ---------- In a fixed width character set codes of all characters have the same number of bytes. Fixed width character sets are: all single-byte character sets and those multibyte character sets which have names ending with 'FIXED'. In Oracle9i the character set AL16UTF16 is also fixed width. In a varying width character set codes of different characters may have different number of bytes. All multibyte character sets except those with names ending with FIXED (and except Oracle9i AL16UTF16 character set) are varying width. Single-byte character sets are character sets with names of the form xxx7yyyyyy and xxx8yyyyyy. Each character code of a single-byte character set occupies exactly one byte. Multibyte character sets are all other character sets (including UTF8). Some -- usually most -- character codes of a multibyte character set occupy more than one byte. CLOB values in a database whose database character set is fixed width are stored in this character set. CLOB values in an Oracle 8.0.x database whose database character set is varying width are not allowed. They have to be NULL. CLOB values in an Oracle >= 8.1.5 database whose database character set is varying width are stored in the fixed width Unicode UCS-2 encoding. The same holds for NCLOB values and the national character set. The UCS-2 storage format of character LOB values, as implemented in Oracle8i, ensures that calculation of character positions in LOB values is fast. Finding the byte offset of a character stored in a varying width character set would require reading the whole LOB value up to this character (possibly 4GB). In the fixed width character sets the byte offsets are simply character offsets multiplied by the number of bytes in a character code. In UCS-2 byte offsets are simply twice the character offsets. As the Unicode character set contains all characters defined in any other Oracle character set, there is no data loss when a CLOB/NCLOB value is converted to UCS-2 from the character set in which it was provided by a client program (usually the NLS_LANG character set). CLOB Values and the Database Character Set Change ------------------------------------------------- In Oracle 8.0.x CLOB values are invalid in varying width character sets. Thus you must delete all CLOB column values before changing the database character set to a varying width character set. In Oracle 8.1.5 and later CLOB values are valid in varying width character sets but they are converted to Unicode UCS-2 before being stored. But UCS-2 encoding is not a binary superset of any other Oracle character set. Even codes of the basic ASCII characters are different, e.g. single-byte code for "A"=0x41 becomes two-byte code 0x0041. This implies that even if the new varying width character set is a binary superset of the old fixed width character set and thus VARCHAR2/LONG character codes remain valid, the fixed width character codes in CLOB values will not longer be valid in UCS-2. As mentioned above, the ALTER DATABASE [NATIONAL] CHARACTER SET statement does not change character codes. Thus, before changing a fixed width database character set to a varying width character set (like UTF8) in Oracle 8.1.5 or later, you first have to export all tables containing non-NULL CLOB columns, then truncate these tables, then change the database character set and, finally, import the tables back to the database. The import step will perform the required conversion. If you omit the steps above, the character set change will succeed in Oracle8(i) (Oracle9i disallows the change in such situation) and the CLOBs may appear to be correctly legible but as their encoding is incorrect, they will cause problems in further operations. For example, CREATE TABLE AS SELECT will not correctly copy such CLOB columns. Also, after installation of the 8.1.7.3 server patchset the CLOB columns will not longer be legible. LONG columns are always stored in the database character set and thus they behave like CHAR/VARCHAR2 in respect to the character set change. BLOBs and BFILEs are binary raw datatypes and their processing does not depend on any Oracle character set setting. NCLOB Values and the National Character Set Change -------------------------------------------------- The above discussion about changing the database character set and exporting and importing CLOB values is theoretically applicable to the change of the national character set and to NCLOB values. But as varying width character sets are not supported as national character sets in Oracle8(i), changing the national character set from a fixed width character set to a varying width character set is not supported at all. Preparing CLOB Columns for the Character Set Change --------------------------------------------------- Take a backup of the database. If using Advanced Replication or deferred transactions functionality, make sure that there are no outstanding deferred transactions with CLOB parameters, i.e. DEFLOB view must have no rows with non-NULL CLOB_COL column; to make sure that replication environment remains consistent use only recommended methods of purging deferred transaction queue, preferably quiescing the replication environment. Then: - If changing the database character set from a fixed width character set to a varying with character set in Oracle 8.0.x, set all CLOB column values to NULL -- you are not allowed to use CLOB columns after the character set change. - If changing the database character set from a fixed width character set to a varying width character set in Oracle 8.1.5 or later, perform table-level export of all tables containing CLOB columns, including SYSTEM's tables. Set NLS_LANG to the old database character set for the Export utility. Then truncate these tables. Restoring CLOB Columns after the Character Set Change ----------------------------------------------------- In Oracle 8.1.5 or later, after changing the character set as described above (steps 3. to 6.), restore CLOB columns exported in step 2. by importing them back into the database. Set NLS_LANG to the old database character set for the Import utility to avoid IMP-16 errors and data loss. RELATED DOCUMENTS: ================== [NOTE:13856.1] V7: Changing the Database Character Set -- This note has limited distribution, please contact Oracle Support [NOTE:62107.1] The National Character Set in Oracle8 [NOTE:119164.1] Changing Database Character set - Valid Superset definitions [NOTE:118242.1] ALERT: Changing the Database or National Character Set Can Corrupt LOB Values <Note.158577.1> NLS_LANG Explained (How Does Client-Server Character Conversion Work?) [NOTE:140014.1] ALERT: Oracle8/8i to Oracle9i using New "AL16UTF16" [NOTE:159657.1] Complete Upgrade Checklist for Manual Upgrades from 8.X / 9.0.1 to Oracle9i (incl. 9.2) [NOTE:124721.1] Migrating an Applications Installation to a New Character Set Oracle8i National Language Support Guide Oracle8i Release 3 (8.1.7) Readme - Section 18.12 "Restricted ALTER DATABASE CHARACTER SET Command Support (CLOB and NCLOB)" Oracle8i Documentation Addendum, Release 3 (8.1.7) - Chapter 3 "New Character Set Scanner Utility" Oracle8i Application Developer's Guide - Large Objects (LOBs), Release 2 - Chapter 2 "Basic Components" Oracle8 Application Developer's Guide, Release 8.0 - Chapter 6 "Large Objects (LOBs)", Section "Introduction to LOBs" Oracle9i Globalization Guide, Release 1 (9.0.1) Oracle9i Database Globalization Guide, Release 2 (9.2) For further NLS / Globalization information you may start here: [NOTE:150091.1] Globalization Technology (NLS) Library index .
 Copyright (c) 1995,2000 Oracle Corporation. All Rights Reserved. Legal Notices and Terms of Use.
Joel P�rez

Mail and Asian fonts set-how to reset...

I am attempting to remote support a client using Apple Mail. He has a Mac Book Air/Lion (not sure if 10.7.4 yet) but my email to him is getting interpted as Asian character set.
I'm thiking of looking within Mail/Preference/Fonts and Colors but the larger issue is what precipitated this in the first place. Shoudl I be looking elsewhere.
Body of the text is Asian font set but the email address and other particualrs from him and me are English.
Should I look at keyboard preferences as well?
Looking for guidance.
Many thanks to all...

He uses Mail/iCloud with an ATT DSL system. I have my own domain using IMAP as well as a .me account using Mail.app.
Waiting to hear when I can remote login to look at things.
Another thought is to backup his mailbox, rebuild, and then do a big purge of his inbox. His work pattern is such that he leaves way too much in his inbox (4K+ messages). I've counseled him to change. If the system is getting corrupted maybe this is a symptom?
Also not sure if he is at 10.7.4-I'm not going there yet due to some nasty issues with the Thunderboldt upgrade released last week.
Thanks

Problem displaying japanese character set in shopping cart smartform

Hi All,
whenever users are entering some text in Japanese character set while creating a shopping cart in SRM, the smartform print output is displaying some junk characters!! even though the system is unicode compatable, did any one have problem ??
Thanks.

Hi,
May be there is some problem with UNICODE conversion.
See the foll links;
Note 548016 - Conversion to Unicode
http://help.sap.com/saphelp_srm50/helpdata/en/9f/fdd13fa69a4921e10000000a1550b0/frameset.htm
Europe Languages work in Non- Unicode System
Re: Multiple Backends
Re: Language issue
Standard Code Pages in Non-Unicode System
Re: Upgrade from EBP 4.0 to SRM 5.0
http://help.sap.com/saphelp_srm50/helpdata/en/e9/c4cc9b03a422428603643ad3e8a5aa/content.htm
http://help.sap.com/saphelp_srm50/helpdata/en/11/395542785de64885c4e84023d93d93/content.htm
BR,
Disha.
Do reward points for useful answers.

Matching across multiple character sets

Would like to know whether anyone has attempted matching across multiple character sets, for example, between English and Japanese: what are the pitfalls to avoid, what are the best practices, and what you would like to see from application/tools perspective as an ideal solution. thanks

If you upgrade to Logic Pro, you'll get WaveBurner as part of the package which helps you do this, including tweaking your pauses between tracks, fades etc.
If you have Toast, you can do it there too.
If you don't have any 3rd. party software, the work around would be to assemble all your songs in order, end to end in a new Logic file, and listen to all your tracks and adjust the relative levels between songs, then bounce out the individual tracks which have volume changes with their new volume settings. Finally you could then use any burning app such as [SimplyBurns|http://bit.ly/c1oglP] to create CDs or bounce them out in Logic with the additional .mp3 option.
Obviously it's important to listen to your material in order, in context, as some songs will be at the wrong subjective level depending on the tracks either side in the placement. This isn't really important in digital distribution where your material probably won't be listened to as a whole, but as individual downloads.

Multiple character sets on a single page

JDev 11.1.1.5 - WLS 10.0.3.5
I have an application that needs to have some fields in a different character set (like Amharic) and some in English.
These are fixed - so when the user enters the field - it should already be in the different language.
I use UTF8 for all my jspx. The fonts are unicode. The database is setup for NVARCHAR.
I am using ADF.
What do I need to do to create this kind of page? Where do I install the fonts? And how do I make the Input Text default to the appropriate character set for display/input?

No, you can only have one <f:view> per JSP page (including any pages that page includes), and the locale must be the same for the complete response (because it's also used when the post-back request is parsed).
It's hard to say from your description if this makes sense or not, but why don't you use static text for the part that is always in German, and only localize the parts of the page that needs it?
Hans Bergsten (EG member)

Website not displaying correctly. Firefox is changing the character set to Western (ISO-8859-1) automatically.

Normally I have set Firefox (or it's set by default) to Character Set Unicode (UTF-8) and everything displays perfectly. I've never had a problem before.
Now however, whenever I upload my own website, for some bizarre reason on that particular tab (and only that tab) the Character Set is changed over to Western (ISO-8859-1) and then there's a few characters within my site that do not display correctly, namely apostrophes and hypens.
It definitely isn't my software (Serif WebPlus X4) because the page displays correctly in every other browser. Plus it displays correctly in Firefox if I change the Character set back to Unicode.
PS The site is a work in progress

That happens because the server sends a content-type (text/html; charset=ISO-8859-1) via the HTTP response headers and in that case that content type prevails. The page code is saved with an UTF-8 byte order mark (ï»¿) that you see in this case.
*http://web-sniffer.net/?url=http%3A%2F%2Fwww.valuevisionglasses.co.uk&http=1.1&gzip=yes&type=HEAD&uak=0
*http://httpd.apache.org/docs/current/mod/mod_mime.html#AddType

Glyph panel not displaying font character sets in cs5.5

Hi
I'm having issues with accessing font character sets & glyphs in ID cs5.5.
I have all my fonts in fontbook and can see the full font character sets displayed but
when I go to my glyph panel to access any additional character or glyphs sets there
is nothing displayed. Any idea where I'm going wrong?
Thank you

You potentially have a "bad" font. Check your fonts and remove the offender.
Mylenium

한글이 ??? 로 DISPLAY 되는 경우(CHARACTER SET)

제품 : SQL*PLUS
작성날짜 : 1996-07-02
한글이 ??? 로 DISPLAY 되는 경우(CHARACTER SET)
=============================================
Oracle Tools(SQL*Plus, Forms 30, Forms 40, Reports 20 등)을 이용하여 한글
DATA를 조회할 때 ???로 출력되는 경우 해결 방법.
DATABASE는 SQL COMMAND 'CREATE DATABASE'를 포함하는 STATEMENT를 수행할
때 만들어지는데 우리가 그 STATEMENT를 수행하기 앞서 고려해야 할 사항 중의
하나가 DB CHARACTERSET이다.
DB를 CREATE할 때 DATABSE CHARACTERSET을 명시해야만 하는데, 한번 선택되고
난 후에는 CHARACTER SET을 변경하는 것은 쉽지가 않다.
DATA DICTIONARY에 있는 DATA를 포함해서 모든 DATA는 선택된 CHARACTERSET에
의해 입출력 되기 때문에 USER가 다른 CHARACTERSET으로 ACCESS한다면 한글 데이
타가 ???로 출력된다.
또한, 분산 DB 환경이나 UPGRADE할 경우에는 DATABASE CHARACTERSET이 같아야
하므로, 사용자들은 DATABASE의 CHARACTERSET을 알아 두어야 한다.
< 현재 DATABASE 의 CHARACTERSET 확인 및 변경 >
1. 데이타베이스 CHARACTERSET 확인
$ sqldba lmode=y
SQLDBA> connect internal
SQLDBA> select * from v$nls_parameters;
PARAMETER VALUE
NLS_CHARACTERSET KO16KSC5601 (or US7ASCII)
(A)
2. 환경 변수의 NLS_LANG 확인
$ env
NLS_LANG=American_America.US7ASCII
(B)
위의 (A)와 (B)가 동일한 경우에만 한글 데이타 처리에 문제가 없으며, 이것이
서로 다른 상태에서 한글 데이타를 조회할 경우에는 ??? 로 출력 된다.
3. CHARACTERSET을 일치시키는 방법
* NLS_LANG 환경 변수를 변경하여 일치시키는 방법
<UNIX>
Bourne shell, k-shell을 사용하는 경우 .profile을 수정한다.
NLS_LANG = American_Amerca.KO16KSC5601; export NLS_LANG
c-chell을 사용하는 경우 .cshrc 혹은 .login 수정
setenv NLS_LANG American_America.KO16KSC5601
수정 후 다시 $env를 실행하여 변경되었는지 확인한다.
<WINDOWS 3.1>
C:\WINDOWS\ORACLE.INI 수정
NLS_LANG=American_America.KO16KSC5601
WINDOW 재기동
<WINDOWS 95>
WINDOWS 95에서는 NLS_LANG이 ORACLE.INI에 들어있지 않고
REGISTRY에 기록되므로 REGISTRY EDITOR를 이용하여 수정해야 한다.
MS DOS 창으로 나가서 REGEDIT.EXE 실행
또는
시작 -> 실행 -> regedit -> HKEY_LOCAL_MACHINE -> SOFTWARE -> ORACLE
오른쪽 마우스 버튼을 이용하여 NLS_LANG을 수정한다.
REGISTRY 변경 후에 PC를 REBOOTING 할 필요는 없습니다.
<WINDOWS NT>
WINDOWS NT 에서도 WINDOWS 95의 경우와 마찬가지로 REGISTRY에 기록된
정보를 변경해 주면 됩니다. 다음과 같이 합니다.
DOS 창에서 REGEDT32.EXE 실행
HKEY_LOCAL_MACHINE -> SOFTWARE -> ORACLE 선택
메뉴를 선택하여 NLS_LANG을 수정
* 서로 다른 character set 을 갖는 DB를 access 하는 client에서는 다음과
같은 setting 을 하면 편리합니다.
예를 들어서 SERVER의 character set이 US7ASCII이고 PC의 NLS_LANG이
American_America.KO16KSC5601과 같이 서로 다르게 설정되어 있는 경우
다음을 각 client의 환경에 추가하면 한글 문제가 해결됩니다.
ORA_NLS_CHARACTERSET_CONVERSION=NO_CHARACTER_SET_CONVERSION

두 디비가 다른 캐랙터 셋을 쓴다고 해도
디비 자체에는 문제가 없다고 보는데 말이죠..
두 플렛폼을 비교한번해보시고요.
그래도 문제가 생긴다면 님 말씀 대로 바꿔보심이.
위에건 그냥 보시라는거고
중요한건 imp,exp할때 약간 조정이 필요할거 같은데 말이죠.

Firefox 4 displays multiple message boxes with "uninstall set'. How do I stop this?

Firefox 4 displays multiple message boxes with "uninstall set'. They cannot be closed and they freeze Firefox. The only way to stop is to END TASK through the Task Manager.
OS: Vista) with all service packs and updates as of 21 Apr 2011. All other browsers and applications are closed.

This issue can be caused by an extension that isn't working properly.
Start Firefox in [[Safe Mode]] to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Tools > Add-ons > Appearance/Themes).
* Don't make any changes on the Safe mode start window.
* https://support.mozilla.com/kb/Safe+Mode
In Firefox 4 you can use one of these to start in [[Safe mode]]:
* Help > Restart with Add-ons Disabled
* Hold down the Shift key while double clicking the Firefox desktop shortcut (Windows)
See:
* [[Troubleshooting extensions and themes]]

Displaying multiple asian character sets?

Similar Messages

Maybe you are looking for