From Mageia wiki
Jump to: navigation, search
Drakconf multiflag.png


This section of the wiki is dedicated to the Mageia translation team and its per-language subteams. It aims to provide all necessary information for wannabe translators and registered contributors: how to join the team, list of translation teams and their members, contact information and howtos for the Mageia translation workflow.

Note: Each translator is part of the Mageia internationalisation team, but is also a member of one or more per-language subteams, which correspond to the language(s) they want to translate to. You should take note of the following abbreviations since we widely use them: “i18n” stands for “internationalisation” and designates the Mageia internationalisation team. “i18n-<language code>” designates a subteam dedicated to the specified language, e.g. i18n-nl for Dutch or i18n-zh_tw for Taiwanese.

How to join the Mageia translation team?

If you want to become a translator, here are the steps to follow so that we can work together effectively:

  1. Create a Mageia account on Mageia Identity Management (if you haven't already done so).
  2. Add your name to this wiki page in the section of the team you want to join.
  3. Subscribe to the international i18n mailing list which is our primary means of communication.
  4. Subscribe to your language team's mailing list if available (use your Mageia account).
  5. Write a mail to i18n-discuss@ml.mageia.org telling us who you are (including your Mageia account username).
  6. Wait until the coordinator of your team approves you.
  7. Start translating.

Translation teams

The current Mageia internationalisation team representatives are Rémi Verschelde (Akien on IRC) and Yuri Chornoivan (yurchor). Each per-language subteam has its own representatives who should attend the i18n team meetings (if possible) and coordinate the workflow of their subteam. These representatives are shown in bold on the I18n teams listing page.

If you wish to join a translation team, please add yourself to the team/s you want to join by entering your name, registered username and contact details. You may also create a new team in the event that it does not yet exist.

For now, it is our only means to keep track of who are our contributors and how to contact them, so please keep it up-to-date.

Important note:
It turns out that many people who added their names to this page are not subscribed to the mageia-i18n mailing list. This list is the main platform for translators where all relevant information is announced. It is therefore useful to subscribe.
A general mail has been sent regarding the set up of the translator teams. Please read this page.


(Outdated list: People having registered for translations)

Translation Statistics and reports

Internal communication

Apart from this wiki, we have several means of communication within the Mageia internationalisation team, such as:

The i18n discuss mailing list

There is a general mailing list for the i18n team: i18n-discuss@ml.mageia.org - this list is for general discussions only. It is mandatory that every translator follows this mailing list, as most of our directives are posted there.

We ask you to write in English only on this list; therefore internal communication within a per-language subteam should be realised through another means of communication (see the next section for subteams mailing lists). To subscribe to the i18n mailing list, follow this link and click on subscribe after loging in.

Subteams mailing list

Thanks to our friendly sysadmins, we now have mailing lists for each language subteam that has requested it for internal communication. Available (requested) so far are the following lists:

Communication on those lists is to be done in the language of the subteam. Use one of the links above to subscribe to the mailing list of your subteam. If your subteam has no mailing list, you can ask for it on the Mageia i18n mailing list. The i18n team leaders will ask the sysadmins to create the requested list.

You may want to read this page about mailing lists settings and usage.

Team meetings

Team meetings within the Mageia internationalisation team are announced on the i18n-discuss mailing list and take place on the #mageia-i18n channel of Freenode's IRC network. Please note: While everybody can attend those meetings, we'd like to keep the active attendants to the team representatives to be able to keep the meeting duration reasonably short. The i18n team leader or deputy will inform their respective teams about meetings (if there is one and what's on the agenda) before the preceding Wednesday evening.

The meetings are logged thanks to MeetBot, and you can find the logs on this page. There may be meetings for your language subteam, but that is up to your team. Please contact your subteam leader for information about potential meetings and IRC channel.

The #mageia-i18n IRC channel

The Mageia internationalisation team has a dedicated channel on Freenode's IRC network, #mageia-i18n. It serves two purposes: it is the place where team meetings occur on Thursdays, and it can be used for casual or translation-related chat (in English) between the i18n team members. Just remember that not every i18n member will read what you post there, so if you have something important to discuss, please use also the i18n mailing list.

How to translate

Transifex

The simplest way to help translating is to use Transifex. It is a web-based translation tool which enables us to have an overview of the status of the work on various projects and to translate online or offline (in this case, using your favorite translation tool). We abbreviate Transifex as Tx
With Transifex, you can easily translate the distribution itself, the help pages and the websites.

Once translated in Tx, the .po files must be committed to Mageia's GIT repository (GIT). Each team has to choose one or two committers, who shall have GIT write access.

Here are some resources for the committers:
Committer guide: How to commit files to the GIT.
For the merging of po files, see here

If there is no one to commit, or for any further information, ask the i18n-discuss mailing list.

Alternative

Tx isn't the only way, moreover, you have to use this alternative if the resource you want to translate is not in Tx yet.

String translation

For the purpose of translating our software (i.e. what we call string translation), the Mageia internationalisation team uses the GNU gettext library, i.e. we translate .po file.

We moved our version control system for source code/translation source to git, so please have a look at the Git usage for l10n and doc page.
You will find a list of translation resources here.


Editing po files

First of all, never edit a pot file, they are automatically generated from the source code and used as a reference only. If you do find an error in a string, please report it on the i18n mailing list.

For editing po files, you can use any text editor but it is better to use a specialist tool like Lokalize (see our great howto about Translating with Lokalize), Virtaal, GTranslator, OmegaT or poedit, because then you can be sure you won't create syntax errors.

Thorough description of the translation file formats and the translation tools can be found in FOSS localisation manual.

Website translation

Global Navigation

You need to translate global navigation for the Web site. You can check out existing translations. You can use the same procedure as for web pages (see bellow).


Web pages
Pages prepared for translation are available in web page translation report.

What you should do: grab the ./en/web_page.pot file, translate the strings, and either send it to the i18n mailing list or commit it directly into a created directory in http://gitweb.mageia.org/web/www/tree/langs/your_language_code/. You can also see in report that you can add translation "by recycling old page" if it already exists. Please remember to replace existing web page file with relative symlink in http://gitweb.mageia.org/web/www/tree/your_language_code/ after git commit of ./your_language_code/web_page.po file in that case. If you're unsure about that just ask on i18n mailing list. After your commit such pages have added sentence "old page still exists!" in report so you can't miss them even if you forget to do that.


NOTE:
Code from the repository will go online within 5 minutes past your commit.

In the case report tells you that some lines are missing you should add them to your po file. Report also tells you the missing lines if you follow the link allowing you to copy/paste it in your po file.


Special cases of web pages
  • For better proofreading of your translation use both links for /en/downloads/get/ page listed on report. That page is actually dynamic and gives different content on regular download and on "file not found" one.
  • Constitution is handled in a different way. There are two things to translate. The first one is short constitution.po file that translates the decoration of the Web page while the actual content of the constitution is in the .md file. The only valid version is the French, original one. All translations are there only for informational purpose. To keep order in this, we need to store it in a single, different place (http://gitweb.mageia.org/org/constitution/tree/ ) in a specific format (Markdown). If you would like to translate it, please submit a new Markdown-formatted doc, translated from the French original (http://gitweb.mageia.org/org/constitution/tree/mageia.org_statutes_fr.md ). It will be pushed to www from this place.
  • License page is also handled differently as it reads translated text for license itself directly from git if it exists. Please translate also warning about unofficial translation there. Note that special sign (\n) for new line in git is converted directly to html equivalent on web page so you have some control of lines length. Besides that drakx *.po file there are just a few strings to translate in license.po file.


Informative status of pages which are not converted to gettext translation system yet

Page Priority Comment
en/charter.html on hold a bit outdated, it will get a significant update about our style guide sooner or latter.
en/1/, en/1/for-you/, en/1/migrate/, en/1/next/, en/1/notes/,
en/downloads/1/, en/downloads/dl_twitter.php
none, EOL Mageia 1 has reached end of life (EOL) in 2012!
en/about/2010-sept-announcement.html none It won't change, ever. So it should not be converted, it's an historical document per se - rda
en/about/founders.html on hold may change completely
en/about/reports/2010/, en/about/reports/2011/, en/about/reports/2012/ on hold significant change expected
en/legal/ on hold not done yet
en/support/report-a-bug/ on hold not linked yet, will likely change

Blog translation

This is up to each per-language subteam.

If there is no instance of Mageia Blog in your language, and you would like to maintain one, please ask the Mageia internationalisation team representatives and they will forward it to the blog team.

Wiki translation

How to write a wiki page