Last modified: 2008-12-30 02:22:12 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 451 - Automatic conversion between simplified and traditional Chinese
Automatic conversion between simplified and traditional Chinese
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Highest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: parser
Depends on:
  Show dependency treegraph
Reported: 2004-09-11 07:56 UTC by Mingli Yuan
Modified: 2008-12-30 02:22 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Mingli Yuan 2004-09-11 07:56:08 UTC
Current Chinese language speakers use two different writing systems - simplified and 
traditional Chinese. Automatic conversion between them is critical for the future of 
Chinese Wikipedia. Current conversion tools such as libiconv convert characters between 
two different encodings, but situation we face now is a conversion inside Unicode. 
Unicode is include both simplified and traditional Chinese characters. for most 
simplified and traditional Chinese characters there exist a one-to-one mapping, but 
there still are about 100 pairs of simplified and traditional Chinese characters which 
are not one-to-one, and there is no space between two adjacent words in a Chinese 
sentence. So completely automatic conversion need some AI features, and is difficult, 
but we can introduce some kind of new markup to solve the problem.
Comment 1 zhengzhu 2004-09-18 03:47:45 UTC
I have been working on this issue lately, and will probably continue to work on
it for a while. There is a test site for this at
Comment 2 Brion Vibber 2008-12-30 02:22:12 UTC
This was implemented some years ago. :)

Note You need to log in before you can comment on or make changes to this bug.