From Fedora Project Wiki

m (1 revision(s))
m (Jibecfed moved page L10N/Tools to Archive:L10N/Tools: old process pre-transifex)
 
(22 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{admon/warning|Outdated|Please refer to the [[L10N]] page or the [[L10N/Guide|L10N user guide]].}}
= The Fedora Localization Project - Tools and Infrastructure =
= The Fedora Localization Project - Tools and Infrastructure =


This an overview of the tools the Fedora Localization Project uses. This is not a complete list.
This an overview of the tools the Fedora Localization Project uses. This is not a complete list.


 
{{Anchor|collaboration}}
 
{{Anchor|Collaboration}}
== Collaboration ==
== Collaboration ==


* We work in teams, with each team being responsible for a language/region. The central place to list teams is at [[L10N/Teams| L10N/Teams]] , which we try to keep more or less up to date. If your team is not listed there, please add it to the table.
* We work in teams, with each team being responsible for a language/region. The central place to list teams is at [[L10N_Teams]], which we try to keep more or less up to date. If your team is not listed there, please file a bug report.
* Another place to see a list of the teams and the languages Fedora is translated to, is at http://translate.fedoraproject.org/teams/.
* Every team should have a maintainer/coordinator. This is the contact point for the team, so that someone could say "thanks!" or "can someone from the team fix file X because it's broken?".
* Every team should have a maintainer/coordinator. This is the contact point for the team, so that someone could say "thanks!" or "can someone from the team fix file X because it's broken?".
* In the future, they maybe managed directly through the XML files of the l10n website. Maintainers ''could'' be members of a special group, <code>cvsl10n-maintainers</code>, to receive automatic notifications of new bugs being opened.
* Maintainers ''could'' be members of a special group, <code>cvsl10n-maintainers</code>, to receive automatic notifications of new bugs being opened.


{{Anchor|website}}
{{Anchor|website}}
== Website ==
== Website ==


* Main website: http://translate.fedoraproject.org/. More info: [[L10N/Tools/Website]] .
* The L10n Admin Group is responsible for the Infrastructure. Its members are [[User:Glezos| Dimitris Glezos]], [[User:Diegobz| Diego Búrigo Zacarão ]], [[User:Asgeirf| Asgeir Frimannsson]], [[User:Ankit| Ankit Patel]].
* Wiki space: [[L10N| http://fedoraproject.org/wiki/L10N/]] .
* Main [https://fedora.transifex.com/ translation management] site, used for viewing translation status.
* There exists a page with [http://fedoraproject.org/wiki/L10N?action=LikePages:all wiki pages under L10N/*] , and also a [[CategoryLocalization| category for L10n]] .
* Wiki space: [[L10N| http://fedoraproject.org/wiki/L10N]].
* Many localization teams/ambassadors and have localized websites, hosted elsewhere. This is normal.
* There exists a [[CategoryLocalization| category for L10n]].
* Transifex (submit translations): https://translate.fedoraproject.org/submit/
* Many localization teams/ambassadors have localized websites, hosted elsewhere. This is normal.


{{Anchor|modules}}
{{Anchor|modules}}
== Repository access for translations ==
== Repository access for translations ==


* All translatable modules related to Fedora are listed on http://translate.fedoraproject.org/module/, together with the repository they are hosted on.
* You can view all [https://fedora.transifex.com/ translation projects], together with the repository they are hosted on.
* Modules hosted outside <code>cvs.fedoraproject.org</code> require special treatment for sending translations. Either you'd use [https://translate.fedoraproject.org/submit/ Transifex] , open an account on the system, or open a bug report for the maintainer to commit your translation.
* Some modules listed in Transifex can't be translated with it. Usually there are instructions for submitting translations in description of specific module. If not, open a bug report for the maintainer to commit your translation.
 
* Project maintainers who would like to receive translations for their project should [[L10N_FAQ#How_do_I_add_a_module_to_Transifex.3F_.28.23add-transifex.29| follow these instructions]].
The following is a rough list of the repos that are related to translations. To see which is used for each module, please refer to: http://translate.fedoraproject.org/module/.
 
{| border="1"
|-
| <code>cvs.fedoraproject.org</code> || This is the main CVS server for Fedora. The accounts are handled by the Fedora Account System; translators are considered all the members of the <code>cvsl10n</code> group.  Instructions for joining the Fedora Localization Project can be found on the page [[L10N/Join| L10N/Join]] . The following three repositories exist in it:
|-
| || <code>/cvs/docs/</code> -- Translators have access to the <code>/po/*</code> subdirectories. To translate Documentation, checkout the appropriate module from the <code>docs</code> repository. For more information, refer to [[DocsProject/Translation| DocsProject/Translation]] .
|-
| || <code>/cvs/l10n</code> -- Translators have access to the whole repo.
|-
| || <code>/cvs/pkgs</code> -- Translators have access to the <code>/po/*</code> subdirectories.
|-
| <code>svn.fedorahosted.org</code> || To submit files, use [https://translate.fedoraproject.org/submit/ Transifex] .
|-
| <code>hg.fedorahosted.org</code> || To submit files, use [https://translate.fedoraproject.org/submit/ Transifex] .
|-
| <code>git.fedorahosted.org</code> || To submit files, use [https://translate.fedoraproject.org/submit/ Transifex] .
|-
| <code>http://linux.duke.edu/yum/git</code> || No direct access for Fedora translators. To submit PO files, open a bug report at <code>bugzilla.redhat.com</code>.
|}
 
* Project maintainers who would like to receive translations for their project should provide translators with access on their Version Control System (CVS, SVN, etc).
* To add a new language, either a Makefile should be edited and the language code should be appended in the appropriate line, or a file called LINGUAS should exist inside the <code>po/</code> directory, which lists the published languages of the module.
* CVS automations usually take place, so that translators can checkout a module containing just the po subdirs instead of the whole source code.


{{Anchor|cvs}}
{{Anchor|cvs}}
== CVS of the FLP ==
== CVS of the Fedora Localization Project ==


The FLP has its own repository, to use it host project-specific resources (like the website, etc).
The FLP has its own repository, to use it host project-specific resources (like the website, etc).


This repo is different from the repositories that host various software the FLP is translating. To see which translatable module is hosted where, refer to http://translate.fedoraproject.org/module/.
This repository is different from the repositories that host various software the FLP is translating.


The project's CVS space is on the [http://cvs.fedoraproject.org/viewcvs/?root=l10n l10n repository] . Members of the <code>cvsl10n</code> group have access to it.
The project's CVS space is on the [http://cvs.fedoraproject.org/viewvc/?root=l10n l10n repository]. Members of the <code>cvsl10n</code> group have access to it.


* Anonymous checkout: <code>:pserver:anonymous@cvs.fedoraproject.org:/cvs/l10n</code>
* Anonymous checkout: <code>:pserver:anonymous@cvs.fedoraproject.org:/cvs/l10n</code>
Line 73: Line 47:
== Bugzilla ==
== Bugzilla ==


* Fedora L10N should be a different Product and each language a component.
Useful Bugzilla pages:
* Useful Bugzilla pages:
* [https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Localization Create a new bug report]
* [https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Localization Create a new bug report]  
* [https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora%20Localization&bug_status=NEEDINFO&bug_status=MODIFIED&bug_status=NEW&bug_status=ASSIGNED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=RELEASE_PENDING&bug_status=POST&bug_status=FAILS_QA List of all open l10n bugs]
* [https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora%20Localization&bug_status=NEEDINFO&bug_status=MODIFIED&bug_status=NEW&bug_status=ASSIGNED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=RELEASE_PENDING&bug_status=POST&bug_status=FAILS_QA List of all open l10n bugs]  
* [https://bugzilla.redhat.com/bugzilla/describecomponents.cgi?product=Fedora%20Localization All Bugzilla L10n components]
* [https://bugzilla.redhat.com/bugzilla/describecomponents.cgi?product=Fedora%20Localization All Bugzilla L10n components]  
* [https://git.fedorahosted.org/cgit/l10n/owners.git/plain/owners.list owners.list file] is in FLP's git.
* [http://cvs.fedoraproject.org/viewcvs/owners/owners.list?root=l10n&rev=1.8&view=markup owners.list file] is in FLP's CVS.


{{Anchor|communication}}
{{Anchor|communication}}
== Communication ==
== Communication ==


=== Mailing list ===
=== Mailing list ===


There are some [http://redhat.com/mailman/listinfo mailing lists] that interest members of the FLP.
There are some [https://admin.fedoraproject.org/mailman/listinfo mailing lists] that interest members of the FLP.


* The main list is [http://www.redhat.com/mailman/listinfo/fedora-trans-list fedora-trans-list] ([http://redhat.com/mailman/listinfo/fedora-trans-list archive] ), which holds discussions about translations, team coordination, etc.
* The main list is [https://admin.fedoraproject.org/mailman/listinfo/trans trans] ([http://lists.fedoraproject.org/pipermail/trans]), which holds discussions about translations, team coordination, etc.
* Technical issues are discussed at [http://www.redhat.com/mailman/listinfo/fedora-i18n-list 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.
* Technical issues are discussed at [https://admin.fedoraproject.org/mailman/listinfo/i18n i18n]. 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.
* Each team with over 2-3 members should have '''it's own''' mailing list. To request this, please [https://fedorahosted.org/fedora-infrastructure open a ticket at fedora infrastructure] . If you are to discuss only translations, a name like <code>fedora-trans-XX</code> is appropriate (eg. fedora-trans-de). If you have bigger plans and would like at some point to address also end-users, a name like <code>fedora-XX-list</code> could be considered.
* Each team with over 2-3 members should have '''it's own''' mailing list. To request this, please [https://fedorahosted.org/fedora-infrastructure open a ticket at fedora infrastructure]. If you are to discuss only translations, a name like <code>trans-XX</code> is appropriate (eg. trans-de). If you have bigger plans and would like at some point to address also end-users, a name like <code>XX-users</code> could be considered.


=== IRC channel ===
=== IRC channel ===


* <code>#fedora-l10n</code> on Freenode
* <code>#fedora-g11n</code> on Freenode


=== Meetings ===
=== Meetings ===


* See: [[L10N/Meetings| L10N/Meetings]]  
* See: [[L10N_Meetings| L10N Meetings]]  


{{Anchor|commits-list}}
{{Anchor|commits-list}}
Line 103: Line 77:


* We've setup the group 'l10n-commits' for those who'd like to receive emails for commits in the <code>/cvs/l10n/</code> repo and various other emails.
* We've setup the group 'l10n-commits' for those who'd like to receive emails for commits in the <code>/cvs/l10n/</code> repo and various other emails.
* To subscribe, go to [https://admin.fedoraproject.org/accounts/userbox.cgi?_edit=1 your account] and add yourself to 'l10n-commits'. Unfortunately the system needs approval, so someone should jump in to approve you, which should happen really soon.
* To subscribe, go to [https://admin.fedoraproject.org/accounts your account] and add yourself to 'l10n-commits'. Unfortunately the system needs approval, so someone should jump in to approve you, which should happen really soon.


----
[[Category:Localization]]
[[Category:Localization]]

Latest revision as of 21:44, 30 August 2019

Outdated
Please refer to the L10N page or the L10N user guide.

The Fedora Localization Project - Tools and Infrastructure

This an overview of the tools the Fedora Localization Project uses. This is not a complete list.

Collaboration

  • We work in teams, with each team being responsible for a language/region. The central place to list teams is at L10N_Teams, which we try to keep more or less up to date. If your team is not listed there, please file a bug report.
  • Every team should have a maintainer/coordinator. This is the contact point for the team, so that someone could say "thanks!" or "can someone from the team fix file X because it's broken?".
  • Maintainers could be members of a special group, cvsl10n-maintainers, to receive automatic notifications of new bugs being opened.

Website

Repository access for translations

  • You can view all translation projects, together with the repository they are hosted on.
  • Some modules listed in Transifex can't be translated with it. Usually there are instructions for submitting translations in description of specific module. If not, open a bug report for the maintainer to commit your translation.
  • Project maintainers who would like to receive translations for their project should follow these instructions.

CVS of the Fedora Localization Project

The FLP has its own repository, to use it host project-specific resources (like the website, etc).

This repository is different from the repositories that host various software the FLP is translating.

The project's CVS space is on the l10n repository. Members of the cvsl10n group have access to it.

  • Anonymous checkout: :pserver:anonymous@cvs.fedoraproject.org:/cvs/l10n
  • Eponymous checkout: export CVSROOT=:ext:<username>@cvs.fedoraproject.org:/cvs/l10n and cvs co <modulename>
  • Update your repository: cvs -z9 up (best done before you start with your translation work)
  • Check your files: msgfmt -c po/<lang>.po
  • Take a look at the status: msgfmt --stat po/<lang>.po
  • Commit your changed files: cvs commit [filename]
  • Add a new file to the CVS: cvs add [filename] then cvs commit [filename]

Bugzilla

Useful Bugzilla pages:

Communication

Mailing list

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

  • The main list is trans ([1]), which holds discussions about translations, team coordination, etc.
  • Technical issues are discussed at i18n. 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.
  • Each team with over 2-3 members should have it's own mailing list. To request this, please open a ticket at fedora infrastructure. If you are to discuss only translations, a name like trans-XX is appropriate (eg. trans-de). If you have bigger plans and would like at some point to address also end-users, a name like XX-users could be considered.

IRC channel

  • #fedora-g11n on Freenode

Meetings

Commits list

  • We've setup the group 'l10n-commits' for those who'd 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 really soon.
Retrieved from "https://fedoraproject.org/w/index.php?title=Archive:L10N/Tools&oldid=551184"