No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
[[I18N/Bugs| Bugs]] [[Communicate| Communicate]] [[I18N/Indic| Indic]] [[I18N/SCIM| SCIM Input Method]] | {{Bubble| | ||
* [[I18N/Bugs| Bugs]] | |||
* [[Communicate| Communicate]] | |||
* [[I18N/Indic| Indic]] | |||
* [[I18N/SCIM| SCIM Input Method]] | |||
* [[Docs/Beats/I18n| Docs Beat]] | |||
* [[SIGs/Fonts| Fonts SIG]] | |||
* [[Lohit| Lohit Indic Fonts Project]] | |||
* [[L10N| Localization Project]] | |||
}} | |||
= The Fedora Internationalization (I18N) Project = | = The Fedora Internationalization (I18N) Project = |
Revision as of 09:11, 24 June 2008
The Fedora Internationalization (I18N) Project
The Fedora I18N project works on internationalization (i18n) to support the localization (l10n) of Fedora in many languages.
Translation of Fedora software and documentation are handled by the Fedora L10N project .
The goals of the Project are to:
- Develop, package, and maintain applications like input methods for different languages
- Improve applications and utilities to support and process different languages
- Quality-assure that existing applications meet i18n standards
- Support the infrastructure of the Fedora translation community
Joining the Fedora Internationalization Project
- To learn how to join Fedora Internationalization Project, please refer to the Join page.
Communication
Mailing List
- fedora-i18n-list - Discussions about internationalization of Fedora core
IRC channel
Meetings
- See our Meetings page.
Technologies
Input Methods
Input Methods are used to input Asian and other languages.
- SCIM is the default multilingual input method framework in Fedora
- m17n maps for Indic and other languages
- uim, a light multilingual input method framework
- gcin for Traditional Chinese
- kinput2 for Japanese
- nabi for Korean
Fonts
- Lohit Project. The Lohit fonts are a family of Indic fonts licensed under GPL.
- Liberation Project The Liberation fonts are a family of Latin, Greek and Cyrillic fonts licensed under a free/libre license.
Adding Language Support
Reporting Bugs
Before you file a bug, please read through the list of current and previous bugs for the corresponding software package to determine if your bug has already been filed. If your bug does not exist, enter a bug report using the Bugzilla bug entry page . If your bug exists and has not been fixed, add additional information to the existing bug. If your bug exists and has been fixed, upgrade to the version in the bug report to determine if the bug was properly fixed. If it was not, reopen the bug.
See the I18n Bugs page for I18n related Bugzilla queries.
See the I18N Bugs Guidelines for reporting bugs.
People
- Akira TAGOH
- Caius Chance - <cchance AT redhat.com>
- Dimitris Glezos
- Jens Petersen
- Lawrence Lim - <llim AT redhat.com>
- Li Zhang
- Parag Nemade
- Pravin Satpute
- Rahul Bhalerao
- Ryo Dairiki
- Sachin Tawniya
- Shawn Peng Huang
- Yu Shao - <yshao AT redhat.com>
- Zheng Hua
- NayyarAhmad