Help:Extension:Translate

This page is a translated version of the page Help:Extension:Translate and the translation is 71% complete.

Outdated translations are marked like this.

Translators (main help page )

Translation administrators

Sysadmins and developers

De Translate extension dey enhance MediaWiki plus essential features dem need make dem do translation work. Dem fi use am translate de content pages, de wiki ein interface den even oda software products, as dem use am for translatewiki.net. De Translate extension dey cam plus easy to use translation interface wey dem fi separate de content structure from de text content wey dey hia make dem translate, e dey show de translatable text per to translators by e dey split de content go manageable units. Dem track each unit automatically for changes, den translators immediately dey see wat dey hia make dem update for specific page anaa thru out de wiki.

Dem dey use de Translate extension make dem translate de MediaWiki ein user interface den oda software projects for translatewiki.net by hundreds of translators every month. For userbase.kde.org dem dey use am translate almost thousand content pages plus user documentation. E be easy make dem start dey use de Translate extension, but for de same tym e san dey scale up den provide advanced reporting, reviewing den workflow features.

Features

Interface: De main feature for de Translate extension be simple yet functional translation interface. Besides de essential information lyk message definition den documentation, you san so fi view translations for oda languages insyd. If dem change definition, you go see de changes. De extension dey come plus sum built-in checks, wey go fi help plus common mistakes lyk unbalanced brackets den unused variables. E dey depend for de configuration top, der san so be suggestions from translation memory den machine translation services lyk those of Google Translate, Microsoft ein Bing Translator den Apertium.

Dem enhance de usability for de translation interface plus JavaScript den AJAX. De backend dey provide WebAPIs wey dem fi use insyd mobile interfaces anaa interfaces dem tailor go specific kind of content. Esan so be possible say you go fi export messages for translation for oda off-line den on-line tools insyd wey dey accept de Gettext po file format.

Message groups den tasks: Dem build chaw of de features around two basic concepts: message groups den tasks.

Sam message group dey represent sam collection of messages. One content page go be one message group, wer, for de simplest form insyd, each paragraph go be one message for dat group insyd. Messages wey dey dem use for each MediaWiki extension form insyd sam message group for translatewiki.net top – sam few of de largest extensions get multiple groups. You san go fi make sam group of groups, lyk All newsletters anaa All Translate extension messages. Chaw statistics den de tasks dey work for de message group basis top.

De tasks, anaa for oda words insyd different listings of messages for sam message group insyd, facilitate different dey use cases. Normally sam translator dey get sam list of all untranslated messages for sam chosen message group insyd, but tasks dey wey you go fi review messages anaa just get sam list of all messages, translated anaa naah.

Reporting den statistics: De extension get extensive reporting features wey dey rang from sam view of untranslated messages across all message groups for sam given language go lists of translators per language plus dema activity level.

Content translation: If you ever try say you go translate content for MediaWiki insyd widout any tools, you know say eneva dey scale. De versions dem translate dey get out of date wey no way dey wey go fi track changes go de master page, so chaw half-translated den outdated translations dey widout clear overview for de overall status. Translators often dey feel discourage if dem no dey fi job plus small manageable pieces of text. Translators no dey find wat dem go job for top anaa wat dey hia make dem update. De users san so dey conf by information wey be outdated.

We dey solve all dis plus de Translate extension den ein page translation feature. Edey add sam bit of overhead for de pages wey dey hia translation top, but de benefits far dey outweigh dis. Essentially you only dey hia say you go mark de parts of de page wey dey hia translation. De extension dey split such parts go paragraph sized units insyd wey edey create sam message group give dem. Afta dat translators go fi use all de features wey dem describe above. For addition you go fi add sam language bar easily plus de ‎<languages /> tag anaa get links automatically make you go de user ein preferred language version (only) if edey exist, by say you go use de links of de form [[Special:MyLanguage/Pagename]].

For more info make pop de tutorial How you go fi set up sam content page for translation den de in-depth documentation of de page translation feature.

Developers: De extension dey cam plus built-in support give chaw common translation file formats, lyk Java properties den Gettext po files. E get extensive set of tools, both in-wiki den for de command line top, make e efficiently import den export translations.

Dey search: Widout search feature, ebe difficult give translators make dem find specific messages dem wan translate. Dey traverse all de translations anaa strings of de project be inefficient. Translators sanso often dey wan make dem check how dem translate specific term for certain language insyd across de project.

Dem solve dis by de special page Special:SearchTranslations. Translators fi find de messages wey dey contain certain terms for any language insyd den filter by various criteria: dis be de default. After dem search, dem fi switch de results go de translations of said messages, for instance make dem find de existing, missing anaa outdated translations of certain term.

Make you Use cases

You fi translate almost anytin plus de Translate extension. Naturally der be specialized tools give translation of certain kind of content lyk video subtitles, wey be better done plus dose tools, but in general Translate dey perform very well plus any kind of text wey dem fi split into messages plus length wey dey range from one word up to one large paragraph. Longer messages cam turn unwieldy make dem translate wey ebe just harder make dem job plus.

De three primary use cases wey de Translate extension dey support be content translation, local interface translation den software translation. Dem cover all of dem for de sections wey dey follow, plus links to tutorials den to reference documentation anaa in-depth topical help wer dey available. Of de three use cases dem utilize de interface translation de least.

Content translation

Chaw wikis get content dem dey like make e be available for multiple languages insyd. Weda just few anaa hundreds of pages, e no dey matter. In order make dem prevent dey waste translator dema tym, make dem mark pages for translation only wen dem be reasonably stable. Each change wey dem go make afterwards fi affect tens anaa hundreds of old translations, wey de tym dem dey hia make dem update dem dey add up. Especially plus volunteer translators, you for be aware of dis aspect, den pect de time dem dey spend make dem make translations den updates, dey avoid unnecessary work. If you dey use de Translate extension take translate pages, you be already well for your way make you dey use de translator tym available for de most effective den 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 <languages /><translate>...</translate> and follow the links, or follow the tutorial How to prepare a page for translation.

Dem go fi aggregate Groups of pages togeda plus de Special:AggregateGroups page.

Local interface translation wey dey multilingual wikis insyd

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 {{int:}} magic word. The translatewiki.net main page and some Wikimedia Commons templates are good examples of this. The magic word {{int:}} 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.

If you dey set dis up currently ebe sam bit more complicated dan content translation wey edey hia software configuration, but dem cover all for de tutorial How you go fi make sam interface message group.

Software translation

The Translate extension is a good fit for translating software interface messages. At translatewiki.net, it is used to translate dozens 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.

Help:Extension:Translate

Features

Make you Use cases

Content translation

Local interface translation wey dey multilingual wikis insyd

Software translation

Further reading den tutorials

For translators den translation administrators

For translation administrators

Reference documents give developers

Features

Make you Use cases

Content translation

Local interface translation wey dey multilingual wikis insyd

Software translation

Further reading den tutorials

For translators den translation administrators

For translation administrators

Reference documents give developers

Related