Chinese characters in keychain access?!?

Just installed Leopard and the appropriate updates on my wife's G5 ppc dual 2.5
right at the bottom of the utilities Chinese writing appears. It is the keychain access app. I know this, as when I search for Keychain Access in Spotlight, it shows up as in the utils folder, and when I double-click it in Spotlight, the app opens in Chinese!
The whole system seems to move to Chinese - e.g. the writing in the menu bar all becomes Chinese! Can anyone kindly help?
I need to try and use the Keychain access as this computer won't automatically join the adsl network on waking. It's impossible to use it in Chinese, obviously, as I don't know a letter of Chinese. I am puzzled why on earth this is happening...

thanks folks -
no, it's not Chinese in the whole system, only keychain access
tried the get info - English is missing - the answer would be, I imagine, in figuring out how to get English recognized by Keychain Access
I unchecked all boxes in "international" in the sys prefs except English - but English still doesn't appear the languages section of the get info of Keychain Access
Am considering doing a complete clean install but of course would rather not. A simpler solution would be really cool!

Similar Messages

Simplified Chinese Characters

Hi,
What do I need in order for my application be able to store and retrieve simplified chinese characters in MS. Access?
thank you in advance

Possible answer: using Font key combos.
- for instance the combination 'x$#' may produce a chinese character that can be stored on the DB in the western font and then rendered by;-
myTextArea.setFont(chinese);
Hope that may help ...

Chinese characters in Notes app became gibberish

I have some notes typed in Chinese while the language setting is in English. Then one day I showed my in-law how to change the language setting to Chinese. After that I changed back the setting to English, now all the chineses characters in Notes look like this
Any suggestions how to fix the problem ? I am using Iphone 5 btw.

thanks folks -
no, it's not Chinese in the whole system, only keychain access
tried the get info - English is missing - the answer would be, I imagine, in figuring out how to get English recognized by Keychain Access
I unchecked all boxes in "international" in the sys prefs except English - but English still doesn't appear the languages section of the get info of Keychain Access
Am considering doing a complete clean install but of course would rather not. A simpler solution would be really cool!

LoadUserProfile() creates a profile with Chinese characters on a remote system

Hi,
I'm working on an application where LoadUserProfile() is being used to remotely load a user profile on a machine. The token being passed to LoadUserProfile() is obtained from LogonUser().
When doing this only with a Domain Admin user which is added in Active Directory, it creates a profile with Chinese characters in the C:\Users\ folder of the remote machine. Note that this happens only when logging in for the first time with
this Domain Admin account remotely on that machine.
// code:
PROFILEINFO pi;
memset((void *) &pi, 0, sizeof(PROFILEINFO));
pi.dwSize = sizeof(PROFILEINFO);
pi.dwFlags = PI_NOUI;
pi.lpUserName = (TCHAR *)strUser; //strUser is the User name, and it shows correctly here when debugging
if (LoadUserProfile(hToken, &pi))
//It is actually successful, and comes here when debugging.
Although the name shows up correctly when debugging (remotely), why is it creating a profile with Chinese characters on the remote machine?
TIA,
Jy

CreateProfile won't load the profile. You need to use LoadUserProfile to load the profile, and you need to query for a roaming profile path to put in the lpProfileInfo parameter if you want to include that as well. You need a token for a
user to call LoadUserProfile, but not a profile handle. LoadUserProfile will populate that for you before it returns if it was successful. See this excerpt from
https://msdn.microsoft.com/en-us/library/windows/desktop/bb762281%28v=vs.85%29.aspx:
Upon successful return, the hProfile member
of PROFILEINFO is
a registry key handle opened to the root of the user's hive. It has been opened with full access (KEY_ALL_ACCESS). If a service that is impersonating a user needs to read or write to the user's registry file, use this handle instead of HKEY_CURRENT_USER.
Do not close thehProfile handle.
Instead, pass it to the UnloadUserProfile function.
This function closes the handle. You should ensure that all handles to keys in the user's registry hive are closed. If you do not close all open registry handles, the user's profile fails to unload. For more information, see Registry
Key Security and Access Rights and Registry
Hives.
WinSDK Support Team Blog: http://blogs.msdn.com/b/winsdk/

Cannot Store Chinese Characters In Oracle 9.2.0.7 Database

Hi,
I'm having trouble localizing my Oracle 9.2.0.7 / ASP web application for our Chinese-speaking users.
My Oracle 9.2.0.7 Database has NLS_NCHAR_CHARACTERSET set to AL16UTF16.
I've set up a test table thus:
CREATE TABLE "TBL_TEST_CH"
field1                          NVARCHAR2(40),
field2                          NVARCHAR2(40)
I have the Chinese character set installed on my database / web server (same box), as well as a test client machine. I can see Chinese characters in my web browser, and can enter them in a test ASP page I've set up. When I execute an insert statement via ADO, the insert statement seems to work, but the result is that the data seems to be stored as upside-down question marks.
I thought perhaps the data was being somehow scrambled between the web app and the database, so I set up an external table import the Chinese data from a Unicode text file:
CREATE TABLE kenny.ch_import
     FIELD1          NVARCHAR2(255),
     FIELD2          NVARCHAR2(255)
     ORGANIZATION EXTERNAL (TYPE oracle_loader
     DEFAULT DIRECTORY ext_dat_dir
     ACCESS PARAMETERS
     (RECORDS DELIMITED BY ":"
     FIELDS TERMINATED BY "~"
     missing field values are null)
     LOCATION (ext_dat_dir:'test_ch.txt'))
     reject limit unlimited
However, when I query the data in the external table using my web application, it comes back with garbage like "ÿþ1" and the like.
To attempt to determine if the database is capable of storing the Chinese characters, I've performed the following test:
1) I insert a Chinese character in an NVARCHAR2 field in my table by using the UNISTR function thus:
insert into tbl_test_ch (field1) values (unistr('\3E00'))
2) I interrogated the value using the dump function thus:
select dump(field1, 1016) FROM tbl_test_ch
I'm struggling to understand the output. Obviously the character set being used is "AL16UTF16" (which I would expect to be able to store Chinese characters), but the return_format argument I've provided to the function (1016) should return the hexadecimal code point of the character that's being stored. I would expect this to be the same as I inserted ("3E00"), but I'm getting the following output:
DUMP(FIELD1,1016)
Typ=1 Len=2 CharacterSet=AL16UTF16: 3e,0
I'd really appreciate any suggestions on what I could do next to determine exactly where the problem lies. I've not been able to convince myself that the database is correctly storing the Chinese character data, but I appreciate equally that the problem could lie elsewhere.
Thanks in advance,
Kenny McEwan.

Thanks, Serguisz.
My technology stack is as follows:
ASP 3.0 web application, running on IIS6.
On the web servier, I have MDAC 2.8 SP2 on Windows Server 2003 SP1.
On the Oracle database server, I have Windows Server 2003 SP1.
My Oracle database version is 9.2.0.7.
The client I've been using in this investigation is Internet Explorer 6.0.2900.
It does look like you're right about characters coming from the application are being corrupted. To support this, I tried to insert the chinese character 博 as well as the Unihan character 中 from a web page in my application. I then used the dump function to interrogate the contents of the field I input to thus:
select dump(field1, 1016) FROM tbl_test_ch
DUMP(FIELD1,1016)
Typ=1 Len=2 CharacterSet=AL16UTF16: 0,bf
Typ=1 Len=2 CharacterSet=AL16UTF16: 0,bf
Both characters seem to have suffered the same corruption.
The problem seems to happen in the other direction as well - even after verifying that the character detailed in the previous post was stored correctly, it is still displayed by my web app as an upside down question mark.
Do you have any suggestions on how to proceed?
Best regards,
Kenny.

Chinese characters in Jdeveloper 11g

I use Jdev 11g to create ADF application to access the BPM standalone 10g.
The userID is in Chinese characters and using it can login BPM.
In Jdeveloper 11g, if I use the following code, it shows error and change the Chinese characters to mess code: "??".
How to show the Chinese characters correctly?
Thanks.
------------------------------------java code--------------------------------------------------
String ss="用户"; // 用户 is Chinese characters
String ss2=new String(ss.getBytes("ISO-8859-1"),"GBK");
System.out.println("1111111111=用户="+ss2);
------------------------------------error message--------------------------------------------
1111111111=??=??

Project properties - compiler , check the encoding value.

Chinese characters in filename

After uploading a file in CV01N with Chinese characters in the filename, it cannot be subsequently opened in CV02N/3N. We get system message 26136 - File C:\xxxxx could not be accessed.
I can copy the file to my PC and open from there. When I do this the Chinese characters in the file name are converted to '#'.
Does anyone what I can do to open the file directly from CV02N/3N?
We are on ECC6, EHP6, SP12 and are Unicode compliant.

Hello Dean,
To be able to use Chinese characters in a file name system locale (i.e. the character set which matches the language of the system locale) must be set to Chinese as well.
Otherwise the characters cannot be processed properly (EN system locale does not know Chinese characters). Hope this helps. The best solution would certainly be to avoid non-ASCII
characters in file names on EN operating systems.
Best regards,
Yuki

"Show password" in Keychain Access not working

When I launch Keychain Access and tick the "Show password:" checkbox for a given Keychain item I get prompted to enter my password. After doing so the password field remains blank.
Anyone else run into this problem? Know a workaround?

I'm getting something like this but when I click "Show Password" I get a mumbojumbo of letters and symbols at least 120 characters and clearly not my passworld. Is this something with Maverick, because I've been having a lot of problems.

Cannot Input and Display Chinese Characters by using ODBC Applications

Dear all,
I am trying to input the Simplified Chinese Characters in the Oracle Database Ver 9.2 running on a UNIX AIX server. The client application we are using is th MS Access 2003 running on a MS Windows XP English version SP 2 without multi-language pack. MS Office 2003 is also an English version.
Database setting is:
NLS_CHARACTERSET=US7ASCII
NLS_NCHAR_CHARACTERSET=AL16UTF16
The Oracle Client used is also ver 9.2 with the ODBC driver ver 9.2. I have tried the following NLS_LANG settings by chaging the registry without any NLS_LANG environment settings:
AMERICAN_AMERICA.ZHT16MSWIN950
AMERICAN_AMERICA.ZHS16GBK
AMERICAN_AMERICA.ZHT16HKSCS
AMERICAN_AMERICA.AL32UTF8
I have tied to load some Chinese Characters in by sqlload and by using the NLS_LANG AMERICAN_AMERICA.ZHT16MSWIN950, AMERICAN_AMERICA.ZHS16GBK and AMERICAN_AMERICA.ZHT16HKSCS, they can be display perfectly in SQLPLUS. But when using the same NLS_LANGs and display in the ACCESS, only ???? are displayed.
When I tried to insert Chinese in ACCESS, the character changed to ???? again. No matter what Chinese characters I inserted by MS ACCESS, the ???? code can be dump with the binary code "03, 0f".
Are there any methods or settings I need to change to make ACCESS an application for inserting and displaying Chinese characters from the Oracle database?
I have tried to set the Non-Unicode setting in the Windows Locale setting:
Chinese (Taiwan) (With AMERICAN_AMERICA.ZHT16MSWIN950),
Chinese (Hong Kong S.A.R) (with AMERICAN_AMERICA.ZHT16HKSCS) and
Chinese (PRC) (with AMERICAN_AMERICA.ZHS16GBK)
when inserting the Chinese Characters by Access. But they all failed with ???? inserted in the DB.
Please kindly advise what should be done.
Thanks.

Are you trying to store the character data in char/varchar2 columns?
If that's the case then you have a problem, since a US7ASCII character set can only handle, well, ascii data.
If you are trying to store the data in columns of nchar datatypes, then there might be a problem with literals because literals are converted to database character set first, before conversion to national (nchar) character set. Such data loss can also happen depending on how binds or oci calls are performed.
You could use the dump() function to verify what's actually stored in a database column, without a db - client conversion happening that may distort the facts.
Example:
SQL> select col, dump(col, 1016) from table where some_condition;

Problem in displaying chinese characters in chinese OS

I have a application that is supposed to run on chinese OS. But i can't seem to make it display in the correct language format, whether its big5 or gb2312.
When saving chinese characters to db, it saves weird characters to the db and retreive the weird characters to be displayed on the web.
Do I need to do any changes to anything ??
Thank you in advance.
current system requirements:
Chinese OS (NT4)
Access DB (English version)
Java / JSP languages
Display big5 or GB2312

Try using varchar

ODBC API SQLBindParameter Bug When Passing Chinese Characters?

Hi Everyone,
I am accessing Oracle 10g database (on Windows XP) from Windows XP machine.
Table TEST_TABLE is defined as
CREATE TABLE TEST_TABLE(NVARCHAR2(255))
Using ODBC (code comes shortly) data are successfully inserted into table using SQLBindParameter to bind parameter values.
The same data can be succesfully read from the table. But the query to retrieve only those rows containing chinese characters simply doesn't work.
I am using SQLBindParameter to bind a parameter placeholder when executing SELECT * FROM TEST_TABLE WHERE C1=?. It simply doesn't find the rows if parameter value contains chinese characters, it only finds rows if parameter contains pure ASCII data.
Am I missing something here? NVARCHAR2 data type should be able to always store unicode data. My database settings are:
NLS_NCHAR_CHARACTERSET=AL16UTF16 and NLS_CHARACTERSET=WE8MSWIN1252
Here is the code:
#include "stdafx.h"
#include <windows.h>
#include <sql.h>
#include <sqlext.h>
#define SQLCheck(x)          if (SQL_SUCCESS != x) {\
                                                            SQLINTEGER native;\
                                                            SQLSMALLINT msgLength;\
                                                            SQLCHAR szState[SQL_MAX_MESSAGE_LENGTH],szErrorMessage[SQL_MAX_MESSAGE_LENGTH];\
                                                            ::SQLError(henvAllConnections,hdbc,hstmt,szState,&native,szErrorMessage,SQL_MAX_MESSAGE_LENGTH,&msgLength);\
                                                            printf("Error state=%s, native=%d, message = %s\n",szState,native,szErrorMessage);\
                                                            DebugBreak();\
#define MAX_CONNECT_LEN 512
int tmain(int argc, TCHAR* argv[])
     SQLRETURN nRetCode     ;
     HENV henvAllConnections;
     HDBC hdbc(0);
     HSTMT hstmt(SQL_NULL_HSTMT);
     //TEST_TABLE is created using the following query CREATE TABLE TEST_TABLE(C1 NVARCHAR2(255))
     nRetCode = ::SQLAllocEnv(&henvAllConnections);
     SQLCheck(nRetCode)
     nRetCode = ::SQLAllocConnect(henvAllConnections, &hdbc);
     SQLCheck(nRetCode)
     HWND hWnd = ::GetDesktopWindow();
     TCHAR szConnectOutput[MAX_CONNECT_LEN];
     TCHAR *pszConnectInput = const_cast<LPTSTR>(_T("DSN=o10 american;UID=no;PWD=no#"));
     SWORD nResult;
     nRetCode = ::SQLDriverConnect(hdbc, hWnd, reinterpret_cast<SQLTCHAR *>(pszConnectInput),
          SQL_NTS, reinterpret_cast<SQLTCHAR *>(szConnectOutput), sizeof(szConnectOutput),
          &nResult, SQL_DRIVER_NOPROMPT);
     SQLCheck(nRetCode)
     nRetCode = ::SQLAllocStmt(hdbc, &hstmt);
     SQLCheck(nRetCode)
     TCHAR* szQuery = T("INSERT INTO TESTTABLE(C1) VALUES(?)");
     nRetCode = ::SQLPrepare(hstmt,reinterpret_cast<UCHAR*>(szQuery), SQL_NTS);
     SQLCheck(nRetCode)
     SQLSMALLINT     DataType,DecimalDigits,Nullable;
     SQLUINTEGER     ParamSize;
     nRetCode = ::SQLDescribeParam(hstmt, 1, &DataType, &ParamSize,&DecimalDigits, &Nullable);
     SQLCheck(nRetCode)
     wchar_t chineseData[6];
     chineseData[0]=0x0023;chineseData[1]=0x0050;chineseData[2]=0x0043;chineseData[3]=0xBA85;chineseData[4]=0xc870;chineseData[5]=0x0000;
     wchar_t asciiData[] = L"test data";
     SQLLEN sqlnts = SQL_NTS;
     nRetCode = ::SQLBindParameter(hstmt, (UWORD)1,SQL_PARAM_INPUT,SQL_C_WCHAR,SQL_WVARCHAR,ParamSize,DecimalDigits,chineseData,static_cast<SQLINTEGER>(wcslen(chineseData) * sizeof(wchar_t)),&sqlnts);
     SQLCheck(nRetCode)
     nRetCode = ::SQLExecute(hstmt);
     SQLCheck(nRetCode)
     nRetCode = ::SQLBindParameter(hstmt, (UWORD)1,SQL_PARAM_INPUT,SQL_C_WCHAR,SQL_WVARCHAR,ParamSize,DecimalDigits,asciiData,static_cast<SQLINTEGER>(wcslen(asciiData) * sizeof(wchar_t)),&sqlnts);
     SQLCheck(nRetCode)
     nRetCode = ::SQLExecute(hstmt);
     SQLCheck(nRetCode)
     nRetCode = SQLFreeStmt(hstmt,SQL_DROP);
     SQLCheck(nRetCode)
     TCHAR* pszSQL = _T("SELECT * FROM TEST_TABLE WHERE C1=?");
     int nMaxLength = 1024;
     SQLLEN lLength = SQL_NTS,dataLen;
     TCHAR lpszFieldName[256];
     SWORD nActualLen,nSQLType,nScale,nNullability;
     SQLULEN     nPrecision;
     SQLSMALLINT nResultCols;
     wchar_t pWData[1024];
     nRetCode = ::SQLAllocStmt(hdbc, &hstmt);
     SQLCheck(nRetCode)
     SQLLEN paramLength = static_cast<SQLINTEGER>(wcslen(chineseData) * sizeof(wchar_t));
     nRetCode = ::SQLBindParameter(hstmt,1,SQL_PARAM_INPUT,SQL_C_WCHAR,SQL_WVARCHAR,nMaxLength,0,chineseData,paramLength,&sqlnts);
     SQLCheck(nRetCode)
     nRetCode = ::SQLExecDirect(hstmt, reinterpret_cast<SQLTCHAR *>(pszSQL), SQL_NTS);
     SQLCheck(nRetCode)
     nRetCode = ::SQLNumResultCols(hstmt, &nResultCols);
     SQLCheck(nRetCode)
     nRetCode = ::SQLDescribeCol(hstmt, 1,     reinterpret_cast<SQLTCHAR *>(lpszFieldName), 255, &nActualLen,&nSQLType,&nPrecision,&nScale,&nNullability);
     SQLCheck(nRetCode)
     nRetCode = ::SQLBindCol(hstmt, 1,     SQL_C_WCHAR, pWData, (nPrecision+1) * sizeof(wchar_t),     &dataLen);
     SQLCheck(nRetCode)
     nRetCode = nRetCode = ::SQLFetch(hstmt);
     if (SQL_NO_DATA_FOUND == nRetCode)
          printf("No data found although data are in the table!\n");
     else
          printf("Found chinese data in the table!\n");
     //now try with another qay of SQLBindParameter, which uses length instead of SQL_NTS
     nRetCode = ::SQLBindParameter(hstmt,1,SQL_PARAM_INPUT,SQL_C_WCHAR,SQL_WVARCHAR,nMaxLength,0,chineseData,paramLength,&paramLength);
     SQLCheck(nRetCode)
     nRetCode = ::SQLExecDirect(hstmt, reinterpret_cast<SQLTCHAR *>(pszSQL), SQL_NTS);
     SQLCheck(nRetCode)
     nRetCode = nRetCode = ::SQLFetch(hstmt);
     if (SQL_NO_DATA_FOUND == nRetCode)
          printf("No chinese data found even using different way of SQLBindParameter, although chinese data are in the table!\n");
     else
          printf("Found chinese data in the table!\n");
     //now try with ascii data
     nRetCode = ::SQLBindParameter(hstmt,1,SQL_PARAM_INPUT,SQL_C_WCHAR,SQL_WVARCHAR,nMaxLength,0,asciiData,static_cast<SQLINTEGER>(wcslen(asciiData) * sizeof(wchar_t)),&sqlnts);
     SQLCheck(nRetCode)
     nRetCode = ::SQLExecDirect(hstmt, reinterpret_cast<SQLTCHAR *>(pszSQL), SQL_NTS);
     SQLCheck(nRetCode)
     nRetCode = ::SQLBindCol(hstmt, 1,     SQL_C_WCHAR, pWData, (nPrecision+1) * sizeof(wchar_t),     &dataLen);
     SQLCheck(nRetCode)
     nRetCode = ::SQLFetch(hstmt);
     if (SQL_NO_DATA_FOUND == nRetCode)
          printf("also didn't found ascii data!\n");
     else
          printf("found ascii data!\n");
     nRetCode = ::SQLFreeStmt(hstmt,SQL_DROP);
     SQLCheck(nRetCode)
     nRetCode = SQLAllocStmt(hdbc,&hstmt);
     SQLCheck(nRetCode)
     //now read all values to prove data are really there
     TCHAR* pszSQLAllDaya = _T("SELECT * FROM TEST_TABLE");
     nRetCode = ::SQLExecDirect(hstmt, reinterpret_cast<SQLTCHAR *>(pszSQLAllDaya), SQL_NTS);
     SQLCheck(nRetCode)
     nRetCode = ::SQLBindCol(hstmt, 1,     SQL_C_WCHAR, pWData, (nPrecision+1) * sizeof(wchar_t),     &dataLen);
     SQLCheck(nRetCode)
     while (SQL_NO_DATA_FOUND != SQLFetch(hstmt))
          printf("data from table %S\n",pWData);
     nRetCode =      ::SQLFreeStmt(hstmt, SQL_DROP);
     SQLCheck(nRetCode)
hstmt = SQL_NULL_HSTMT;
     ::SQLDisconnect(hdbc);
     ::SQLFreeConnect(hdbc);
     ::SQLFreeEnv(henvAllConnections);
     return 0;
Regards,
Darko

Hi Darko,
You are right, I think you have discovered a bug in the 10.1.0.2 ODBC driver. I believe this problem is described in Bug 3249731.
The good news is that this is already fixed in the 10.1.0.3 ODBC driver. Do you have access to MetaLink? Goto patches and download "Patchset 3842783" which is the ORACLE ODBC INSTANT CLIENT DRIVER PATCH VERSION 10.1.0.3.0
Good Luck
Nat

Coldfusion 9 not showing some chinese characters

We had web based application made in coldfusion 5 hosted on windows 2000 server. Now we have migrated our application on Coldfusion 9 and windows 2003 server. The problem we are facing is that some chinese characters are showing incorrectly on application pages. we have tried installing language pack and also there is no issue with browser.
Can anybody help us in this regard? Thanks in advance.

craptastic, the forums ate my whole posting because of a stray quoted email marker. this posting was supposed to be:
first off, you need to use the access for unicode driver. secondly, cf5 didn't
know unicode from a hole in the ground & the only way for it use unicode or any
non-latin-1 page encoding is by basically garbaging the data as far as any
unicode compliant application goes (cf6 & above). if you still have the cf5
server, write some cf pages to extract the data from the access db then
re-import it on the cf 9 server. finally, access? really?

Retrieving network password in Keychain Access?

I just upgraded to Snow Leopard and moved.
I used to have the password for the new network stored on my Keychain Access. Now, however, when I try to log on, I'm asked for the password.
I went to look for the password in Keychain Access, and there is a password listed, but it's a long string of lower case letters and numbers -- it looks like some sort of code, rather than the original password.
Is there any way I can translate that long string into the real password? Or any way I can restore the old password?
Thanks for any help.

Susan, you will probably by now have done what you said you were to do and set the airport from scratch. Nevertheless there is no harm in setting up the router his sister left. No need to worry about the keychain for this. Clear, that is "reset' to factory defaults as I believe Direwolf was saying. Then start again. Reset by using the button on the back of the router. You then use the default password and admin username (probably on the soleplate of the router). Download user manual from web if need be.
When I look in keychain for wireless passwords, I see plain text, but I use plain text WPA2 passwords, poetry in lower case no spaces no punctuation and 62 characters long. His sister may have set a hexadecimal password. Someone I know keeps changing her ISP (in Spain). I keep re setting the collection of routers she gets from the ISPs with the same settings so she has four 'plug and play' routers in case one fails.

I can't get iTunes (Mac OS X) to display chinese characters properly...

Hi, I suppose it is because of the ID3 Tags being not properly read by itunes right? cos my Mac can display chinese no problems, specially it can display the mp3 files with it's chinese title in the Mac OS X Mountain Lion Finder no problem!
I have tried somethning called the "Unicode Rewriter", tried converting using Source Encoding as : Big5, Big5_HKSCS, Cp9xx, EUC_TW, ISO2022CN_CNS, MS950... everthing they had for Chinese Traditional Encoding... They all showed up in itunes in Chinese Characters after converison, but it is not the correct word... somethimes it changed even into Korean!
I read about ID3Mod2 but it costs 8US$, and I am not even sure it will work!?While the Unicode Rewriter is Free! but i dont understand why it didn't work though... it seem to be doing what it is suppose to, but just the encoding is maybe not the right one!?
Anybody experiencing the same type of problem and found a solution?
Thanks for your help

Oh I forgot to mention that I'm using a straight cable as resource to the network. I do have access to the internet and some other networkdisks, But I can't access the main one, which is described above.
Thanks!

Traditional and Simplified Chinese characters couldn't be displayed!

Hi all,
Recently I installed an Oracle 9i Database Server (9.0.1).
Problem regarding the globalization support issue was encountered after the installation of Oracle 9i Database Server. Parameters in NLS table had been checked that the language is initially set to AMERICAN, territory is set to AMERICA and the character set is UTF8.
Since traditional and simplified chinese characters must be required for the HK server, it is believed that the above parameters should be altered to TRADITIONAL CHINESE / SIMPLIFIED CHINESE, HONG KONG and ZHT16MSWIN950 / ZHS16CGB231280 respectively.
I tried to alter the NLS_DATABASE_PARAMETERS, but its not working; should the NLS_SESSION_PARAMETERS be changed instead? I also tried this one, changes is taken place but the chinese characters still couldn't be displayed, just bunches of 亂碼 (meaningless codes) instead.
Another piece of information is that the Oracle server is installed on the basis of Windows Server 2003 Standard Edition, should the Language for non-Unicode programs (which is in the Advanced page of the Regional and Language Settings) be configured to Chinese (HKSAR)? Various combinations, in terms of English (US), Chinese (HKSAR), Chinese (PRC), Chinese (Taiwan), had been taken turns to test for the results. However, same results happened.
Hence, how should we configure? Please advice us.
P.S.# It is known that this question should be placed in the "Globalization Support" forum, I have done that; however, it is hoped that I could seek more advice in here.
Thx in advance.
Karen

Karen,
Setting up such an environment requires some sophistication and know how. I would advise reading though the Globalization Support Guide and som of the papers on the Globalization Home Page http://www.oracle.com/technology/tech/globalization/index.html
before randomly attempting to change parameters. If your requirement is to store and retrieve both TRADITIONAL and SIMPLIFIED CHINESE then your database needs to be Unicode (UTF-8). Designing an application that allows you to easily access multilingual data requires careful design and planning. If you are simply trying to quickly display data you have in your database you might want to use iSQL*PLUS which is browser based and will allow you to display Unicode data. It might also be helpful to take a look at the following paper: http://www.oracle.com/technology/tech/globalization/pdf/globalization-best-practices.PDF

Chinese characters in keychain access?!?

Similar Messages

Maybe you are looking for