From Fedora Project Wiki

(Installing/Removing Language Support using dnf)
Line 90: Line 90:
See the page [[I18N/LanguageSupportCriteria|Language Support Criteria]] for the process (steps) for adding i18n support for a new language to Fedora.
See the page [[I18N/LanguageSupportCriteria|Language Support Criteria]] for the process (steps) for adding i18n support for a new language to Fedora.


=== Installing/Removing Language Support using Yum ===
=== Installing/Removing Language Support using Yum/Dnf ===
See [https://fedoraproject.org/wiki/I18N/Language_Support_Using_Yum this] for Installing/Removing Language Support using yum.
See [https://fedoraproject.org/wiki/I18N/Language_Support_Using_Yum this] for Installing/Removing Language Support using yum.
See [https://fedoraproject.org/wiki/I18N/Language_Support_Using_Dnf this] for Installing/Removing Language Support using dnf.


=== Region wise Language Support Matrix ===
=== Region wise Language Support Matrix ===

Revision as of 05:17, 19 February 2015

Contributing roles in the Internationalization (I18N) Project

Contributing roles
These are only suggestions for contributing roles. Only your imagination sets the limits.


OS Developer


Translator

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 Localization Project

Vision Statement

"Fedora i18n makes technology accessible and attractive for users of every language"

Joining the Fedora Internationalization Project

  • To learn how to join Fedora Internationalization Project, please refer to our Join page.

Communication

Mailing Lists

  • i18n list - Discussions about internationalization of Fedora
  • i18n-bugs list - Fedora i18n bugs list

IRC channel

#fedora-i18n[?] on freenode.net

Meetings

Tasks

  • Support the latest Unicode standard

Packages

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 SCM Admin request.

Technologies

Input Methods

Input Methods are used to input Asian and other languages.

Fonts

A page of the Fonts Special Interest Group

  • 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. The Lohit fonts are a family of Indic fonts licensed under OFL 1.1.
  • Liberation Project The Liberation fonts are a family of Latin, Greek and Cyrillic fonts licensed under a free/libre license.
Pango language order
The language priority order that pango uses to render text can be set with the environment variable PANGO_LANGUAGE. For example setting PANGO_LANGUAGE to "ja:zh:ko" would prefer Japanese fonts, then Chinese and then Korean.


Fonts in Fedora
The Fonts SIG takes loving care of Fedora fonts. Please join this special interest group if you are interested in creating, improving, packaging, or just suggesting a font. Any help will be appreciated.

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/Dnf

See this for Installing/Removing Language Support using yum. See this for Installing/Removing Language Support using dnf.

Region wise Language Support Matrix

See this region wise Language Support matrix.

Reporting Bugs

The latest bug stats can be found in the dashboard sections of the meeting agenda pages.

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

Active contributors/maintainers

Former contributors