Forum Moderators: open
Now I'm left to decide between Simplified and Traditional Chinese.
I think I want to align myself with Wikipedia's approach, and use the Chinese they use.
Would somebody who knows Chinese be able to tell me what type of Chinese is used at [zh.wikipedia.org...]
I tried using translators with Simplified and Traditional settings, figuring the one that translated better would be the matching script. But both seemed to work.
I know that translations and internationalization are a pretty big topics, with lots of aspects that need much focus, including localization to specific markets.
With my understanding, Chinese uses the language code zh. But that doesn't seem to fully represent the problem. I know there are at least two major character sets, one thats Traditional, and one that is Simplified, and that different parts of Chinese speaking countries use one or the other.
I see Wikipeida's Chinese website at zh.wikipedia.org, and I'm wondering, how do they get away with it? How are they dealing with the Traditional/Simplified Chinese divide?
I'm thinking about translating into both, with one folder called "zh", and the other with a different title. But I wanted to use zh for the same type of Chinese characters that wikipedia calls zh.
Anyone have any ideas?
Thanks.
The Chinese script (Hanzi) is used in its simplified variant throughout the PRC, and in its traditional version in other Chinese-speaking areas such as Hong Kong and Taiwan.
A site targeting that market has unique special considerations that you need to look at. There are several useful threads covering this topic here, many of which are listed in our Golden Threads [webmasterworld.com].
I tried using translators with Simplified and Traditional settings, figuring the one that translated better would be the matching script. But both seemed to work.
My PC is set up for Korean & Chinese script, so are there urls in Chinese script?
However, in order for such URIs to be used your users have to be using compatible browsers with the appropriate plug-ins. To assure universal access you'd be better off using standard ASCII domain names and paths.
In regards to translating, you might consider other options instead of machine/software translation which has usually a lower level of accuracy. hope this helps.
[edited by: Woz at 10:04 pm (utc) on Jan. 22, 2007]
[edit reason] No URLs please, see TOS#13 [/edit]