Help:Extension:Translate/fr



L’extension Traduire apporte à MediaWiki des fonctionnalités de base pour effectuer du travail de traduction. Elle peut être utilisée pour traduire les pages de contenu, l’interface du wiki ou même d’autres logiciels, comme sur translatewiki.net. L’extension Traduire apporte une interface de traduction facile à utiliser et permet de dissocier la structure du contenu par rapport à la langue du contenu, lorsque celui-ce requiert une traduction. Il est alors montré aux traducteurs que le texte à traduire, après séparation du contenu en petites unités. Les modifications de chaque unité sont automatiquement suivies et les traducteurs voient immédiatement ce qui doit être mis à jour sur une page spécifique ou dans le wiki.

L’extension Traduire est utilisée par des centaines de traducteurs chaque mois sur translatewiki.net pour traduire l’interface utilisateur de MediaWiki ainsi que d’autres projets de logiciels. Sur userbase.kde.org, elle est utilisée pour traduire près d’un millier de pages relatives à la documentation utilisateur. Il est facile de commencer à utiliser l’extension Traduire ; néanmoins elle permet aussi une utilisation poussée et fournit des fonctionnalités avancées de compte-rendu, de relecture et de workflow.

Fonctionnalités


Interface : La fonctionnalité principale de l'extension Traduire est une interface de traduction simple mais efficace. En plus des informations essentielles telles que la définition du message et sa documentation, vous pouvez également voir les traductions dans d'autres langues. Si une définition a changé, vous pourrez voir les modifications. L'extension fournit un mécanisme de vérification intégré, qui peut permettre de détecter des erreurs fréquentes, comme des parenthèses non-fermées ou des variables non-utilisées. Selon le paramétrage, il peut également y avoir des suggestions depuis les traductions précédentes et des services de traduction automatisée comme ceux de Google Traduction, Bing Translator de Microsoft et Apertium.

The usability of the translation interface is enhanced with JavaScript and AJAX. The backend provides WebAPIs than can be used in mobile interfaces or interfaces tailored to specific kind of content. It is also possible to export messages for translation in other off-line and on-line tools that accept the Gettext po file format.

Groupes de message et de tâche: La plupart des fonctionnalités sont conçues autour de deux principes fondamentaux: les groupes de message et de tâche.

Un groupe de messages représente un ensemble de messages. Une page de contenu correspond à un groupe de messages où, dans le cas le plus simple, chaque paragraphe est un message de ce groupe. Les messages utilisés dans chaque extension MediaWiki forment un groupe de messages sur translatewiki.net ; certaines des extensions les plus importantes ont plusieurs groupes. Il est aussi possible de faire un groupe de groupes, tel que Toutes les newsletters ou Tous les messages de l'extension Traduire. Un grand nombre de statistiques et de tâches fonctionnent sur des groupes de messages

Les tâches, ou en d'autres termes les différentes listes de messages dans un groupe de message, facilitent divers cas d'usage. Normalement un traducteur obtient une liste de tous les messages non traduits dans un groupe de message sélectionné, mais il y a des tâches où vous pouvez revoir les messages ou juste obtenir une liste de tous les messages, traduits ou non.



Reporting and statistics: The extension has extensive reporting features ranging from a view of untranslated messages across all message groups in a given language to lists of translators per language with their activity level.

Content translation: If you have ever tried to translate content in MediaWiki without any tools, you know it does not scale. The translated versions get out of date and there is no way to track changes to the master page, so there are many half-translated and outdated translations without a clear overview of the overall status. Translators often feel discouraged when they can not work with small manageable pieces of text. Translators don't find what to work on or what needs updating. The users also get confused by outdated information.

This is all solved with the Translate extension and its page translation feature. It adds a bit of overhead to the pages that need translation, but the benefits far outweigh this. Essentially you only need to mark the parts of the page that need translation. The extension then splits such parts into paragraph sized units and creates a message group for them. After that translators can use all the features described above. In addition you can easily add a language bar with the tag or have links automatically go to the user's preferred language version (only) when it exists, by using links of the form Special:MyLanguage/Pagename.

Pour plus d'informations voir le tutoriel Comment mettre en place une page de contenu pour la traduction et la documentation approfondie sur la fonctionnalité de traduction de page.

Developers: The extension comes with built-in support for many common translation file formats, like Java properties and Gettext po files. It has an extensive set of tools, both in-wiki and on the command line, to efficiently import and export translations.

Cas d'utilisation
You can translate almost anything with the Translate extension. Naturally there are specialized tools for translation of certain kind of content like video subtitles, that are better done with those tools, but in general Translate performs very well with any kind of text that can be split into messages with length ranging from one word up to one large paragraph. Longer messages become unwieldy to translate and are just harder to work with.

The three primary use cases that the Translate extension supports are content translation, local interface translation and software translation. All of them are covered in the following sections, with links to tutorials and to reference documentation or in-depth topical help where available. Of the three use cases the interface translation has been utilized the least.

Traduction de contenu


Most wikis have content they would like to be available in multiple languages. Whether just a few or hundreds of pages, it doesn't matter. In order to prevent wasting translator's time, pages should be marked for translation only when they are reasonably stable. Each change that is made afterwards can affect tens or hundreds of old translations, and the time needed to update them adds up. Especially with volunteer translators, you should be aware of this aspect, and respect the time they spend making translations and updates, avoiding unnecessary work. If you use the Translate extension to translate pages, you are already well on your way to using the translator time available in the most effective and efficient way.

The way the Translate extension splits up a page into paragraph sized units does not leave too much freedom for translators to change the content. This is usually a good thing and is ideal where continuity and consistency of content across languages is desired. It can be worked around, but in principle this way of doing translations is not generally suitable, for example, for Wikipedia articles, which usually are totally independent of each other. Even if they originally start as a translation from a different language, they usually begin living their own independent life from the original version. With Translate, the original page is always the main version, and new content cannot be developed in translated versions.

With these limitations in mind there are still plenty of cases where this feature is a perfect match. Most, if not all, user documentation falls into this category as well as news-like content that does not change once written. If you have the Translate extension already installed and access rights configured, try creating a page and wrapping the whole text inside  and follow the links, or follow the tutorial How to prepare a page for translation.

Traduction de l'interface locale de wikis multilingues
One thing almost every wiki has customized is the sidebar. It is possible to create a message group for the custom sidebar messages and also for other local interface customisations.

One interesting expansion is the multilingual pages or templates built with the magic word. The translatewiki.net main page and some Wikimedia Commons templates are good examples of this. The magic word is an alternative to the content translation feature and it is more suitable to mark-up heavy pages just like the translatewiki.net main page. Another nice feature is that the language of the page automatically follows the user interface language, so there is no need for a language bar, although you might want to have an interface language selector instead.

Setting this up is currently a bit more complicated than content translation and needs software configuration, but it is all covered in the tutorial How to make an interface message group.

Traduction de logiciels
The Translate extension is a good fit for translating software interface messages. At translatewiki.net, it is used to translate tens of software products from games to web applications. The Translate extension supports reading and updating translations from and to common formats used in web development including Java properties, Gettext and Yaml files.

Change tracking is also available for externally tracked files, because internally the extension uses a cached derivative version of the localisation files where the source text and its translations are stored, instead of using them directly in their original format. Translation administrators can either use the web interface or a command line interface to check new message definitions and "fuzzy" (request update of) translations when they need updating. This works regardless of the underlying file format or version control system (if any).

With simple command line tools, translation administrators can easily import even a large set of existing translations and with just one command they can export all translations in the correct format and in the correct directory structure. You can export directly to your VCS repository checkout, where you can easily commit changes and new files.

For translators and translation administrators

 * How to translate [Tutorial]
 * Translation best practices
 * Statistics and reporting
 * Quality assurance
 * Message group states
 * Off-line translation
 * [In progress] Glossary

For translation administrators

 * How to prepare a page for translation [Tutoriel]
 * Administration de la page de traduction
 * Interface message groups (localised sidebar, main page and templates) [Tutoriel]
 * [En cours] Gestion des messages de groupe
 * YAML configuration format
 * How to write YAML configuration for file based message groups [Tutoriel]

Documents de référence les développeurs

 * Installation
 * Configuration
 * [En cours] La traduction expliquée aux développeurs
 * Hooks
 * [En cours] Groupes de message
 * [En cours] Support des formats de fichiers
 * Translation aids
 * [Non écrit] API web
 * Translation memories

Related

 * Translation notifications
 * Localisation/Tutorial: General localisation tutorial for developers, for use at hackathons & trainings
 * Extension:TranslateSvg: Adds support for translating SVG files
 * Universal Language Selector: Provides webfonts and input methods

A faire

 * Implementation on Meta: m:Meta:Translate extension.
 * See translate-doc for specific tasks.