Contributing roles in the 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 Localization Project
Joining the Fedora Internationalization Project
- To learn how to join Fedora Internationalization Project, please refer to the Join page.
- See our Meetings page.
- kbd/im desktop integration
- scm/koji commit mails to i18n-bugs
- update remaining fonts to current guidelines
- Unicode 5.2 and 6.0
- (gdm locale/kbd UI improvements)
Fedora I18n maintains a lot of Fedora packages related to i18n. There is a FAS pseudo-user i18n-team to help track our bugs.
For new approved i18n packages please use "InitialCC: i18n-team" in your CVSAdmin request.
Input Methods are used to input Asian and other languages.
- See I18N/Fonts for Asian fonts in Fedora
- there are many free/libre international fonts, already referenced in fontconfig defaults or packaged by other major distributions, languishing in the Fedora wishlist in wait for a packager.
- 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
Minimum Criteria For Language Support (I18N)
See the page Language Support Criteria for the process (steps) for adding i18n support for a new language to Fedora.
Installing/Removing Language Support using Yum
See this for Installing/Removing Language Support using yum.
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.
- Agustin Ferrario (Pycrash)
- Akira TAGOH
- Anish Patil
- Jens Petersen
- Caius 'kaio' Chance
- Ding-Yi Chen
- Parag Nemade
- Pravin Satpute
- Naveen Kumar
- Dan Mashal
- Ryo Dairiki
- Peng Huang
- Dimitris Glezos
- Lawrence Lim - <llim AT redhat.com>
- Rahul Bhalerao
- Yu Shao - <yshao AT redhat.com>
- Zheng Hua
- A S Alam
- Satyabrata Maitra
- Gao Hu
- Takao Fujiwara
- Peng Wu
- Anson Cheung
- Constantin DRABO
- Lijun Li - <lijli AT redhat.com>
- Mike FABIAN
- Eduardo Mayorga Téllez
- Daiki Ueno