L10N

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (1 revision(s))
(Joining the Fedora Localization Project: formatting table)
Line 17: Line 17:
 
{| border="1"
 
{| border="1"
 
|- style=" color: #fff; background-color: #3074c2;" tablewidth="98%"  
 
|- style=" color: #fff; background-color: #3074c2;" tablewidth="98%"  
| '''New Translator''' || '''Old Translators'''BR  
+
| '''New Translator''' || '''Old Translators'''<BR>''(from i18n.redhat.com)'' || '''other ways to help'''
|~-(from i18n.redhat.com)-~ || '''other ways to help'''
+
 
|-
 
|-
 
| - [http://docs.fedoraproject.org/translation-quick-start-guide/ Translation Quick Start Guide]  - TQSG (updated, see v0.4.1)<BR>- [http://fedoraproject.org/wiki/L10N/Tools#head-96a1095f59c288948d6eb5ef20a509771d7da576 Repository Access] <BR>- [[L10N/CVSBasics|  CVS Basics]] <BR>- [[L10N/FAQ| FAQ]] <BR> - [http://fedoraproject.org/wiki/Languages#head-7aa19e11813d65124cfd24537f9ed548e025d65d Website Translation] <BR> - [http://l10n.kde.org/docs/translation-howto/ KDE Translation HOWTO] <BR> - [http://developer.gnome.org/projects/gtp/resources.html GNOME L10n Resources] <BR> - [http://www.gnu.org/software/gettext/manual/gettext.html GNU gettext Manual]  || - [http://fedoraproject.org/wiki/L10N/Tools#head-96a1095f59c288948d6eb5ef20a509771d7da576 Repository Access] <BR>- [http://docs.fedoraproject.org/translation-quick-start-guide/ TQSG]  (updated, see v0.4.1)<BR>- [[L10N/FAQ| FAQ]] <BR> - [http://fedoraproject.org/wiki/L10N/GUI GUI page] <BR><BR> || - [[L10N#head-bac6b6eb413fd81ad0bd66901870a23684edf87e|  Bug Reporting]] <BR>- Become a [[L10N/Maintainer| Maintainer]] <BR>- [[L10N/Maintenance| Project Maintenance]]
 
| - [http://docs.fedoraproject.org/translation-quick-start-guide/ Translation Quick Start Guide]  - TQSG (updated, see v0.4.1)<BR>- [http://fedoraproject.org/wiki/L10N/Tools#head-96a1095f59c288948d6eb5ef20a509771d7da576 Repository Access] <BR>- [[L10N/CVSBasics|  CVS Basics]] <BR>- [[L10N/FAQ| FAQ]] <BR> - [http://fedoraproject.org/wiki/Languages#head-7aa19e11813d65124cfd24537f9ed548e025d65d Website Translation] <BR> - [http://l10n.kde.org/docs/translation-howto/ KDE Translation HOWTO] <BR> - [http://developer.gnome.org/projects/gtp/resources.html GNOME L10n Resources] <BR> - [http://www.gnu.org/software/gettext/manual/gettext.html GNU gettext Manual]  || - [http://fedoraproject.org/wiki/L10N/Tools#head-96a1095f59c288948d6eb5ef20a509771d7da576 Repository Access] <BR>- [http://docs.fedoraproject.org/translation-quick-start-guide/ TQSG]  (updated, see v0.4.1)<BR>- [[L10N/FAQ| FAQ]] <BR> - [http://fedoraproject.org/wiki/L10N/GUI GUI page] <BR><BR> || - [[L10N#head-bac6b6eb413fd81ad0bd66901870a23684edf87e|  Bug Reporting]] <BR>- Become a [[L10N/Maintainer| Maintainer]] <BR>- [[L10N/Maintenance| Project Maintenance]]
Line 28: Line 27:
 
Some more links:
 
Some more links:
  
* [[L10N/Tools| Tools used by Fedora Localization Project]]  
+
* [[L10N/Tools| Tools used by Fedora Localization Project]]
 
+
  
 
== Teams ==
 
== Teams ==

Revision as of 15:05, 25 May 2008

Contents

The Fedora Localization Project

The goal of the Fedora Localization Project (FLP) is to bring everything around Fedora (the Software, Documentation, Websites and culture) closer to local communities (countries, languages and in general cultural groups). Usually this involves doing translations via PO files but is certainly not limited to that.


Language list

Refer to http://translate.fedoraproject.org/languages for an overview of how many languages are available and have substantial translation of our essential software.


Joining the Fedora Localization Project

To learn how to join Fedora Localization Project, please refer to the Join page.


New Translator Old Translators
(from i18n.redhat.com)
other ways to help
- Translation Quick Start Guide - TQSG (updated, see v0.4.1)
- Repository Access
- CVS Basics
- FAQ
- Website Translation
- KDE Translation HOWTO
- GNOME L10n Resources
- GNU gettext Manual
- Repository Access
- TQSG (updated, see v0.4.1)
- FAQ
- GUI page

- Bug Reporting
- Become a Maintainer
- Project Maintenance

Some more links:

Teams

Communication

Mailing list

There are some mailing lists that interest members of the FLP.

  • The main list is fedora-trans-list (archive ), which holds discussions about translations, team coordination, etc.
  • Technical issues are discussed at fedora-i18n-list . If you are interested in more than translations, like eg. our websites, bugzilla, the mailing list, etc, you would want to join this as well.

Commits list

  • We've setup the group 'l10n-commits' for those who would like to receive emails for commits in the /cvs/l10n/ repo and various other emails.
  • To subscribe, go to your account and add yourself to 'l10n-commits'. Unfortunately the system needs approval, so someone should jump in to approve you, which should happen quickly.

IRC channel

Meetings

Schedule

Both of these schedules include translation freeze dates, which are dates that translations are picked up for adding them into the product.

Tasks

Take a look at the L10N/Tasks page and add your name next to an item you are interested in helping out.


Fedora L10N Steering Committee

The Fedora Localization Steering Committee (FLSCo) leads the Fedora Localization Project (FLP). Its mission is to provide the Fedora translators with necessary guidance, and support their efforts to localize the Fedora Project to multiple languages and cultures.

If you have a question, need clarifications or have problems, please contact Fedora L10N Steering Committee.

Details about the Fedora L10N Steering Committee FLSCo agenda

Bug Reporting, Testing, and Quality Assurance

Before you file a bug, please read through the list of current and previous bugs for the cooresponding software package to determine if your bug has already been filed. If your bug does not exists, 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.

Useful Bugzilla pages:

Some other interesting Bugzilla queries: