From Mageia wiki
Jump to: navigation, search

Esta sección wiki está dedicada a los quipos (team) traductores de Mageia, por lenguaje y por sub-equipos (sub-team). Esto apunta a proveer toda la información necesaria para quienes traducir y contribuyentes registrados: Como unirse a un equipo, lista de los equipos de traducción y sus miembros, información de contacto y guías instructivas (howtos) para que la traducción en equipo de Mageia sea fluida.

Nota: Cada traductor es parte del equipo de internacionalización de Mageia (internationalisation team), pero tambien es un miembro de uno o mas sub-equipos por lenguas, los cuales corresponden a los lenguajes que quieren traducir. Deberías saber las siguientes abreviaciones, dado el hecho de que las usamos abiertamente: “i18n” por "internacionalización" y designa al equipo de intenalización de Mageia. “i18n-<código de lenguaje>” designa al sub-equipo dedicado al lenguaje especificado, ej. il18-nl por Alemán o il18n-zh_tw por taiwanés.

¿Cómo me uno al equipo de traducción de Mageia?

Si quieres convertirte en traductor, aquí están los pasos a seguir, de manera que podamos trabajar juntos efectivamente.

  1. Crea una cuenta de Mageia en Mageia Identity Management (si aún no tienes una.)
  2. Agrega tu nombre a ésta página wiki en la sección del equipo al que te quieras unir.
  3. Regístrate a la lista de correo international i18n mailing-list la cual es nuestra primaria forma de comunicación.
  4. Regístrate a la lista de mail de tu equipo de idioma language team's mailing list de estar disponible (usa tu cuenta de Mageia).
  5. Escribe un mail a diciendo quien eres (incluyendo el usuario de tu cuenta de Mageia).
  6. Espera a que el coordinador de tu equipo te apruebe.
  7. Comienza a traducir.

Equipos de traducción

El actual equipo de internacionalización de Mageia está representado por Oliver Burger (líder, obgr,seneca en IRC) y Rémi Verschelde (director, Akien en IRC). Cada sub-equipo de lenguaje tiene sus propios representantes los cuales deberían atender a las reuniones i18n (de ser prosible) y coordinar el flujo de trabajo de su sub-equipo. Sus nombres están escritos en fuente tipográfica bold, en esta página.

Por favor agrega tu nombre a la siguiente página si aún estás dispuesto a unirte a un equipo de traducción. Agregate en el equipo al que te quieras unir con tu nombre, nombre de usuario registrado y contacto. Tal vez quieras un nuevo equipo, en el caso que aún no exista.

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.

Mageia translation teams and their members
(Outdated list: People having registered for translations)

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

Internal communication

Apart from this wiki, we have several means of communication among the Mageia internationalisation team.

The i18n discuss mailing list

There is a general mailing list for the i18n team: - this list is for general discussions only. It is mandatory that every translator follows this mailing list, for 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 login in.

Subteams mailing list

Thanks to our friendly sysadmins, we now have mailing lists for each language subteam which has requested it for internal communication. Available (or 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.

Teams meetings

Teams meetings of the Mageia internationalisation team are on every second Thursday evenings at 17:30 UTC (19:30 Paris time) 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 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.


String translation

At the moment we are using svn directly, so have a look at the svn for translators page.
You will find a list of translation resources here.

Committer guide: How to commit files on the SVN.

For the merging of po files (problems with Tx since March 2012), see here

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). The only difference is that you need to commit it to and for now also to

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

What you should do: grab the web_page.en.lang file, translate the strings, and either send it to the i18n mailing list or commit it directly into a created directory in You can 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 after svn commit of web_page.your_language_code.lang 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.

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

If you're sure that string is the same as in English (for example a very common word like "Blog") and you like nice statistics (eg. no untranslated strings) you can add " {ok}" on the end of such string (for given example "Blog {ok}").

In the case report tells you that some lines are missing you should add them to your lang file. Report also tells you the missing lines if you follow the link allowing you to copy/paste it in your lang file. It's easier to change it in the long run and more transparent if you add missing lines to your lang file at the same place as in the English version. It's nice to fix the comments that precede (e.g. # /en/about/index.php +69) to reflect the English ones for easier navigation and reference to the source files. Do not forget to add your translated line after the each line you add.

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.*.lang 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 ( ) in a specific format (Markdown). If you would like to translate it, please submit a new Markdown-formatted doc, translated from the French original ( ). 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 svn if it exists. Please translate also warning about unofficial translation there. Note that special sign (\n) for new line in svn is converted directly to html equivalent on web page so you have some control of lines length. Besides that *.po file there are just a few strings to translate in license.*.lang file.

Informative status of pages which are not converted to lang 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