Traditional Chinese character?

We all know that the support for Traditional Chinese is excluded in iPad, make no difference to me since I don't use Chinese, both Simplified Chinese or Traditional Chinese character. But I still would like to know, Can iPad English version view well when I browsing some Traditional Chinese web sites?
Thanks in advance.
PS. By the way, I am NOT a Chinese, we just had no choice to use China's language, Chinese(government, people and language) is no good, they are just like Burma, North Korea, Chinese government control people's lives and death.
PS2. I'm from Formosa (Taiwan), Taiwan has been an independent country since 1949. but sadly, CNP(aka KMT) they love to kiss China's ***, and they killed many innocent Taiwanese from 1949~1999 too. Just a brief to let you know where I came from. because I think it's important, I considered ourselves as a big Apple family.

I still would like to know, Can iPad English version view well when I browsing some Traditional Chinese web sites?
Yes. The iPad has no problem displaying Traditional Chinese (or any of the other languages that the iPhone handles). Examples of scripts which the iPad (like the iPhone) cannot yet display correctly are Devanagari, Bengali, Tamil, and Tibetan.

Similar Messages

Does MuVo N200 fully support Traditional Chinese charact

I wonder if MuVo Micro N200 sold in the UK fully support Traditional Chinese character and some Asian languages such as Japanese(both in showing MP3 file/song name and in user interface)?
Or, I can only get UK-spec N200 and it only shows English/European Languages?

No, the unicode support have bugs for reading the id3 tags.
Some characters are missed sometimes.
Its no good.

Adobe Reader X does not recognise Traditional Chinese Character

The Adobe Reader X does not recognise Traditional Chinese character and directs me to download Japanese fonts. I downloaded Japanese fonts and also Traditional Chinese fonts but it still doesn't work.
Anyone can help?

This topic may also hold some answers: http://forums.adobe.com/thread/1138688

Can iPad English version view Traditional Chinese character?

We all know that the support for Traditional Chinese is excluded in iPad, make no difference to me since I don't use Chinese, both Simplified Chinese or Traditional Chinese character. But I still would like to know, Can iPad English version view well when I browsing some Traditional Chinese web sites?
(I couldn't find an iPad forum, so I came to here, I hope you don't mind)
Thanks in advance.

Can iPad English version view well when I browsing some Traditional Chinese web sites?
There is just no way to know until somebody has one in their hands and tries it, which will probably not be until the end of March.
Generally there is no "English" version of Apple products, their capabilities are the same no matter where they are sold.

Acrobat Reader cannot display Traditional Chinese Character correctly in 64 bit Windows 7

Hi,
I get a pdf file cannot display chinese character properly in Windows 7 64 bit but Windows XP 32 bit. I did uninstall and re-install Reader 9.4.3 and 10.0.1 with and without Traditional Fonts patch in the 64 bit machine but no luck. Does anyone have a solution for this?
Thanks in advance.

I run Acrobat 9.3.3 on my Windows 7 Pro 64-bit system with no problems. Perhaps you should make sure you have all of Acrobat 9's maintenance installed.
Ken Friedman

Traditional Chinese character display as square mark in workflow tab page

Customer applied 11i ATG RUP7(6241631), then run the AD Administration utility to maintain multilingual tables, and no errors when upgrading EBS.
Some tab page title and button text display as square mark.
Please help!
Thanks in adv,
Jackie

Hi,
Please check below notes which could be helpful for your issue
After Korean Language Installation Oracle Apps Displays All Characters As Squares [ID 731894.1]
Chinese Display as Square on the Form Menu after Apply NLS Patch 6678700_ZHT [ID 839957.1]
Chinese Characters are displayed as Empty Squares using Courier New Font [ID 578656.1]
Regard
Helios

Wrong Chinese character

In my Nokia 5800, v21.0.101, the Chinese character "福" is wrongly displayed in the traditional Chinese character format. The same word should be identical with the simplified Chinese character format, which is correctly displayed in the same handset.
A lot of Chinese folks treasure their culture a lot, and such a mistake may not be tolerable to them.
Joe Chan

You should report this to Nokia via the "contact us" tab at the top of the page. Nokia does not monitor these forums for bugs or issues.
Ravi

Traditional Chinese Language (Character Input)

Assuming the Mac can display Traditional Chinese, then it can be said that it can also input Traditional Chinese.
-Do you still have the same options as you do for PC?
(e.g 'Chang Jie', 'Quick' and 'New Phonetic')
or
-Is it through Mac, and is completely different?

then it can be said that it can also input
Traditional Chinese.
-Do you still have the same options as you do for PC?
(e.g 'Chang Jie', 'Quick' and 'New Phonetic')
You can find all the info about the TCIM here:
http://www.yale.edu/chinesemac/pages/tcim_x4.html

Chinese Character Printing in Smartform (Different Question)

Hi all,
Can anyone explain to me further the OSS Note 776507 that Anji Reddy Vangala recently posted? It involves the preview and printing of different character sets. Currently I've managed to preview my form correctly, but it still prints out #'s. Do I need to re-assign the fonts to the printer device or something, or do I need to use a different printer? The printer I am currently using is an HP 2100. Please please help, anyone?
EDIT: Probably a better question would be how to map the conversion font of CNSONG to something that can be read by the printer?
A copy of the note for everyone's reference:
OSS Note: 776507
Symptom
Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?
Other terms
SAPscript, SmartForms, printing, device types, OTF
Reason and Prerequisites
Help required to choose proper fonts in a SAPscript or SmartForm
Solution
When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:
1) The language version of the form used to produce the printout.
Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.
2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).
Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.
3) The output character set of the device type
Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.
A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.
Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.
As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.
4) The set of available printer fonts for a given device type
When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.
To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.
If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.
Note on SAPscript/SmartForms Print Preview:
The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.
A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.
Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.
Which fonts are suitable for a given language?
Language(s): Font family to use in a form:
Latin-1 (Western Europe/Americas) *******
DE,EN,FR,ES,NL,SV COURIER, HELVE, TIMES
(LETGOTH, LNPRINT)
Latin-2 (Central Europe) ****************
PL, CZ COURIER, HELVE, TIMES
ISO 8859-4 (Baltic) *********************
ET, LT, LV COURIER, HELVE, TIMES
ISO 8859-5 (Cyrillic) *******************
BG, RU, SR, UK COURCYR, HELVCYR, TIMECYR
ISO 8859-7 (Greek) **********************
EL COUR_I7, HELV_I7, TIME_I7
ISO 8859-8 (Hebrew) *********************
HE COURIER, HELVE, TIMES
ISO 8859-9 (Turkish) ********************
TR COURIER, HELVE, TIMES
Simplified Chinese **********************
ZH CNHEI, CNKAI, CNSONG
Japanese ********************************
JA JPMINCHO, DBMINCHO, DBGOTHIC
Korean **********************************
KP KPBATANG, KPDODUM, KPGULIM
KPGUNGSE, KPSAMMUL
Traditional Chinese *********************
ZF TWDPHEI, TWMING, TWSONG
Thai ************************************
TH THANGSAN, THDRAFT, THVIJIT
Arabic (Unicode systems only) ***********
AR ANDALE_J
Verify your output by examining the OTF data
When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.
The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu
Goto->Display Requests->Settings
and choose
Display Mode: Raw
Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.
Here is an excerpt from a sample OTF file where we highlight the most interesting commands:
//XHPLJ8000 0700 00000000001
IN04EALEXTEST_ZEBRA
IN05%PAGE1
OPDINA4 P 144 240 1683811906000010000100001
IN06%WINDOW2
MT0024401289
CP11000000E
FCHELVE 120 00109XSF100SF101110000067E X
UL +0000000000000
SW00067
CT00000000
ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit
The 1st line with the // (Control) command reveals the device type usedto print: HPLJ8000
//XHPLJ8000 0700 00000000001
The 2nd line (IN = Info command) shows the name and (internal 1-char)language key of the form:
IN04EALEXTEST_ZEBRA
In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA
The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:
OPDINA4 P 144 240 1683811906000010000100001
The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.
CP11000000E
Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.
FCHELVE 120 00109XSF100SF101110000067E X

Hi,
there a different things to know.
I produce sapscript forms with cinese and english characters for frontend / backend and archiv printing.
Please check:
Editor displays ###: You have to install the chinese language in your e.g. windows-system to display them.
Script: You have to chose the the font family "CNSONG" (customized for chinese simplified and LATIN).
Transaction I18N: May you have to set correct subfonts for the unicode areas (Cascading fonts, Standard is Courier).
You can print in different ways:
For archiv/PDF: Install the unicode truetype font with chinese characters for the pdf-converter.
For Frontend: Use the Frontendprinter SAPWIN or SAPWIN*CF (Cascading Font) to send it to the gui (note: SAPLPD does not support it, use the newer technology.....)
Backend printing: POSTSCRIPT is not yet implemented :-((
PLease note: What you see in spool / print preview is a simulation of the possible print, but backend print is not frontend preview!!!!
Regards,
Christian

Chinese Character in PDF format for Oracle Reports 11g

Hello Everyone,
Currently we have a Report that need to be display chinese character in PDF format.
We followed the steps specified in the "Oralce Fusion Middleware Publishing Reports to the Web with Oracle Reports Services"
documentation but things doesn't work. We also installed Adobe Acrobat Reader 9 and Asian Font Pack 9 on the server side
and even on the client/user/development side and followed the steps in the documentation, but no effect at all. Or we even
tried "Arial Unicode MS", same thing no effect.
For sure, we may miss something during PDF aliasing or PDF subsetting setup.
Anyone out there who has the same experience and able to resolve the issue that currently using the Oralce Fusion Middleware Reports 11g?
Doesn't matter if it does not related to chinese character, as long as it relates to this issue like japanese or arabic characters in PDF.
If its ok, kindly provide the steps how you do it.
Your help is highly appreciated.
Regards and Thank you very much!

I am now facing exactly the same problem as user449955 (Eric's). Dear Eric, how about your situation? If you have resolved this problem, may I ask for your solution?
In my case, using either font aliasing or font subsetting doesn't work at all (displaying "garbage" characters instead of Chinese characters). The setting in my uifont.ali is as follows:
If using font aliasing:
[PDF]
.....ZHT16HKSCS = "MSungStd-Light-Acro"
If using font subsetting (the REPORTS_PATH already includes "C:\Windows\Fonts"):
[PDF:Subset]
"Courier New" = "mingliu.ttc,2"
For both cases, the report server's NLS_LANG already set to "TRADITIONAL CHINESE_HONG KONG.ZHT16HKSCS" (I am in fact located at Hong Kong). For font aliasing, the client side already has Asian Adobe Reader with Asian font pack installed.
By the way, I noticed that the WebLogic EM is configuring/updating the uifont.ali file at "<instance home>\config\FRComponent\frcommon\tools\common" directory, but the Oracle Reports 11g's documentation sometimes advise to refer to another uifont.ali file located at "<instance home>\config\FRComponent\frcommon\guicommon\tk\admin" directory. Which one of the uifont.ali files is the one used by the Oracle Reporting Service?
My report server's platform is Windows 7 Enterprise (64-bit) and the Reports version is 11.1.1.3.
Anyone can help to advise?
Thank you very much.
Regards

Is it possible to read/write Chinese character into Oracle 8i(WE8ISO8859P1) in Applet

I can display Chinese character in swing label or text field, however, when I read
the Chinese character data from (or write to) Oracle DB, it shows ??? instead. I can't
change the code page of my DB, (if use ZHT16Big5 instead of WE8Iso8859P1 as the DB page
code, than everything is OK. :< ) is there any solution for this?
Server:
DB:Oracle8i(8.1.6)with Character set: WE8ISO8859P1
System Environment:NLS_LANG=American_America.WE9ISO8859P1
OS: Win2000 Advance Server(NLS:950 Traditional Chinese)
client:
Applet (written by JDeveloper 3.2) compiled with code: ISO8859_1
JDBC Driver: Oracle JDBC Thin Driver (ver 8.1.7 or 8.1.6)
Browser: IE5.5 (with code Western Europe(ISO) or UTF-8 or Traditional Chinese...)
null

Eric,
There is no good way to do this. In your ASP/ADO application I think you are creating a garbage in garbage out situation. Because the client NLS_LANG matches the DB characterset no conversion takes place. Therefore your chinese characters get inserted in the DB. But the data is really garbage.
When you use Java thin driver a conversion automatically takes place from UCS-2 -> WE8ISO8859P1. The Chinese characters in UCS-2 have no equivalent code point in WE8ISO8859P1, so you end up with replacement characters ??

Display problem when reading Traditional Chinese in Crystal Report 2008

Hi All,
I have tried to connect MS SQL 6.5 to build up a report. However, I encounter a problem when read Traditional Chinese. all chinese characters turn into adnormal characters. I wonder it is problem of SQL Server or some setting that I may not know. In addition, I can able to read chinese in the application program , ISQL / Query Analyzer. Please help to give idea and suggestion to fix this. Thanks
SQL Server: MS SQL Server 6.5
Client OS: Window XP ( Traditional Chinese Version)
Server OS: Window NT and Window Server 2000
Stsyou

Hi
If you are using a Chinese language build database, Crystal Reports English build might not display the characters properly as non english databases include one byte characters as ASCII code character and double-byte characters as their own language code character.
Traditional Chinese, Simplified Chinese, Japanese (Kanji, Hiranga, and Katakana), Korean and Vietnamese use double-byte characters.
However, a possible workaround to this issue is to verify that the encoding on the database client is configured according to the examples below. Also, you will need to install the language pack in the English environment.
CONFIGURATION EXAMPLES:
Shift-JIS for a Japanese database
Big5 for a Traditional Chinese database
GB2312 for a Simplified Chinese database
iso-2022-kr for a Korean database
Windows 1258 for a Vietnamese database
EXAMPLE SCENARIO:
An Oracle database saves non-English language data such as Japanese.
The Windows operating system is English.
STEP TO CONFIGURE THE CHARACTER CODE IN THE ENVIRONMENT SETTING
(This step is based on the details of the EXAMPLE SCENARIO.)
1. Configure the system environment on the database client side to 'Shift-JIS' as the character code set in the Environment Setting.
This results in the NLS_LANG variable set to Japanese_Japan.JA16SJIS under the registry HKEY_Local_Machine\Software\Oracle\Homeo.
STEPS TO INSTALL LANGUAGE PACK IN AN ENGLISH ENVIRONMENT
(These steps are based on the details of the EXAMPLE SCENARIO.)
1. Add languages to the computer system by clicking:
Control Panel > Regional Options > General
2. Select the check box for 'Traditional Chinese', 'Simplified Chinese', 'Japanese', 'Korean' or 'Vietnamese'.
3. Click 'Apply'.
4. When you are prompted, insert the Windows CD-ROM to install the language pack.
5. Restart the computer.
Upon completing these steps, you are able to display the languages characters in the Crystal Reports Designer in a Windows English environment.
==========
NOTE:
If the database table and field names use non-English language characters, Data Explorer in CR will not correctly display these names. However, when you preview the report, the non-English data displays correctly.
==========
Configuring the database client according to the examples and installing the language pack will display the characters successfully. However, there are cases when this workaround does not resolve the issue.
For further information about CR and double-byte languages, refer to knowledge base articles, c2008083 and c2008349.
Hope this helps!!!
Regards
Sourashree

Chinese character in PDF output file ?

I have trouble to display Chinese characters (traditional Chinese) on PDF output file. Is there anyone can help ?

<BLOCKQUOTE>quote:<HR>Originally posted by Rene Kello ([email protected]):
From 'Reports 6i Release Notes'...
Reports supports PDF 1.1.
The Adobe Acrobat Reader cannot read .PDF report files generated by Report Builder if the report contains certain types of non- English character set languages (typically multi-byte) or Unicode character set.
Same with reports 6.
Install Acrobat Reader 4.X. Print to Acrobat Distiller printer. Works for Baltics.
cheers,
Rene.<HR></BLOCKQUOTE>
It works ! Thank you !

Chinese Character display issue on Coldfusion 10

My Company using Coldfusion to built an report platform and recently I upgrade our Coldfusion 7MX with Windows Server 2003 to Coldfusion 10 Enterprise with Windosw Server 2008 R2.
I copy the Code from the Old server to the new one, but I met the problem I couldn’t solve.
We have a repost that can enter, modify and view our SRM that has Chinese Character display request. Chinese character was display without problem when the system in the old server. which look like following.
once I move the code into the new server, I got the problem with Chinese Character as following.
This report pulling the data from SQL2005 with Windows Server 2003 R2.
Coldfusion code code was same and both version is access to the same database.
I ran all of the update included to install the windows MUI for Chinese character into the new server, but I still can't get the character display correctly.
I can view the chinese character website without issue but only to display in the report.
I contact with Microsoft tech support but they don't have an solution for me. please help.

Install windows server language pack: http://www.microsoft.com/en-us/download/details.aspx?id=12250
Are you sure the Chinese is encoded in UTF-8? (It should be, but you should check the database field type encoding.) If it's simplified chinese it could be set to GB18030 and if it's traditional chinese it could be Big5.
You might want to leave off the encoding directive in CF and load the page in a browser then change encodings using tools > encodings to see what works.
祝你好运！

Nls_lang for psp with Traditional Chinese

I have two Oracle environments:
1. Oracle 817 on Windows 2000 (eng) with Traditional Chinese as default locale, and
2. Oracle 816 on Solaris with Oracle 9iAS portal.
in both environment, I wanted to create a simple page as follows:
<html>
<head>
<title>Welcome</title>
<meta http-equiv="content-type" content="text/html; charset=big5">
</head>
<body>
<h3>Welcome to this page</h3>
Welcome Here
</body>
</html>
If I put this page under a virtual directory of Apache, the client browser would change the encoding to Traditional Chinese (Big 5) if "Auto-Select" is selected in encoding. Now, I try to put this in a psp. The page comes up with encoding change to "Western European (ISO)". I view the source from the page and it is just the same as the one under a virtual directory of Apache.
Why does this happen?
How can I make the client browser change to "Traditional Chinese (Big 5)" encoding?
I tried to set the NLS_LANG before using loadpsp but that didn't make any difference. Any idea?

Do you mean that I will have problem later if I don't change the database character set?Yes , definitely. What you are doing is storing invalid multibyte characters into a single byte database. So each double byte BIG5 characters are being treated as 2 separate WE8ISO8859P1 (Latin1) characters. You are using an unsupported but common garbage in garbage out approach, so in that sense you are using Oracle as a garbage container :) .
Let's look at some of the issues that you are going to have :-
All SQL Functions are based on the property on the database character set WE8ISO8859P1. So LENGTH(), SUBSTR (), INSTR (), UPPER(), NLS_UPPER etc .. will yield incorrect results . For example a column with one BIG5 character and one ASCII character will return a length of 3 characters rather than 2 characters. And if you want to locate a specific character in a mix ASCII and BIG5 string using the SUBSTR() it will be very difficult, because to Oracle the string consists of all single byte Latin1 characters, it will not skip 2 bytes for a BIG5 character. Even if you don't have mix strings, you will need to have one routine for handling ASCII only and another for BIG5 strings.
Invalid Data conversion , if your need to talk to another db using dblink say ,all the character conversion will be based on Latin1 to the target database character set mapping, so the receiver will lose all the source BIG5 characters and will get 2 Latin1 characters for each BIG5 char instead .
Export and Import will have identical problems, character set conversion are performed during these operations, so all BIG5 characters will be lost. This also means that you can not load BIG5 data into your current DB using IMPORT or SQLLOADER without data corruption ...
null

Traditional Chinese character?

Similar Messages

Maybe you are looking for