#19950 closed defect (bug) (worksforme)
Support the Uyghur translation
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | lowest | |
| Severity: | normal | Version: | |
| Component: | I18N | Keywords: | |
| Focuses: | Cc: |
Description
The Uyghur translation (ug_CN) bends over backwards to be compatible with WordPress. Because there is so much going on here, I need to pull it out into its own ticket.
Given the complexities here (I will post a diff shortly), and because they compose about 1/10th of one percent of non-English downloads, I don't see this happening for 3.4.
Attachments (1)
Change History (4)
#1
@
13 years ago
Uighur has two big problem on Web Browser:
- Character connectivity: some Uighur character cannot connect properly in some OS, even in Arial or Tahoma. It is a font problem so we must use our own font.
- Text Input: even an Uighur Input Method added from Windows Vista, but the 70% of Uighur have to use Windows XP with IE6 in China. User unable to input Uighur characters on this OS. So we must add a keyboard hook in the purpose of Uighur text input.
Up to now, these problems solved by Uighur Translation Team every time.
This ticket was mentioned in IRC in #wordpress-dev by nacin. View the logs.
11 years ago
#3
@
9 years ago
- Milestone Future Release deleted
- Resolution set to worksforme
- Status changed from new to closed
The latest version on https://ug.wordpress.org/releases/ is 4.1, and it doesn't have any of these changes.
Also, the home page of the site says that the translation is no longer active.
Feel free to reopen if still relevant.
Diff against 3.3.1. I reverted all changes made irrelevant by #19598 or elsewhere. I also left out the font files, which you can find at http://i18n.svn.wordpress.org/ug_CN/trunk/dist/wp-content/languages/.