Help:Extension:Translate/da



Translate-udvidelsen forbedrer en MediaWiki wiki med vigtige funktioner, der kræves for at udføre oversættelsesarbejde og kan benyttes til at oversætte indholdssider, ​​wiki-brugergrænsefladen og andre software-produkter, som det for eks. ses i translatewiki.net/da. Translate udvidelsen udgives med en nem brugbar oversætter-brugergrænseflade som kan adskille indholds-struktur fra indholds-sprog, der skal oversættes, og viser kun teksten der kan oversættes til oversætteren ved at opdele indholdet i håndterbare enheder. Hver enhed spores automatisk for ændringer, og oversættere ser straks, hvad der behøver opdatering på en bestemt side eller hele wikien.

Translate-udvidelsen bruges til at oversætte brugergrænsefladen i MediaWiki og andre software-projekter på translatewiki.net, med hundredvis af oversættelen om måneden. På [//userbase.kde.org userbase.kde.org] er det brugt til at oversætte næsten 1000 indholdssider med brugerdokumentation. Det er let at begynde med at bruge Translate-udvidelsen, som samtidig vokser og giver mulighed for avanceret rapportering, revidering og strømlinede funktioner.

Funktioner


Brugerflade: Det vigtigste træk ved Translate-udvidelsen er en enkel, men funktionel oversættelses-brugerflade. Udover de væsentlige oplysninger såsom besked-definition og dokumentation, så du kan se oversættelser på andre sprog. Hvis en definition har ændret sig, vil du se ændringerne. Udvidelsen kommer med nogle indbyggede kontrol-funktioner, der kan hjælpe med almindelige fejl som uafsluttede parenteser og ubrugte variabler. Afhængigt af konfigurationen, er der også forslag fra oversættelseshukommelsen og maskinoversættelse-tjenester, som dem i Google Translate, Microsofts Bing Translator og Apertium.

Anvendeligheden af oversættelses-dialogen er forbedret med JavaScript og AJAX, men redigering af beskeder i en normal side redigeringsvindue er også understøttet. Alle oversættelses-hjælpefunktioner er understøttet i begge visninger. Oversættelse er ikke engang begrænset til disse brugergrænseflader! Det er også muligt at eksportere meddelelser til oversættelse i andre off-line og on-line værktøjer, der accepterer Gettext po formatet. Desuden er der en Web API, som kan anvendes til at bygge specielle grænseflader.

Nyhedsgrupper og opgaver: Mange af funktionerne er bygget op omkring to grundlæggende begreber: Nyhedsgrupper og opgaver.

En nyhedsgruppe repræsenterer en samling af meddelelser. En indholdsside ville være en nyhedsgruppe hvor, i den enkleste form, hvert afsnit ville være et budskab i gruppen. Meddelelser, der anvendes i en MediaWiki udvidelse, danner en nyhedsgruppe på translatewiki.net - et par af de største udvidelser har flere grupper. Du kan også lave en gruppe af grupper, som for eks. Alle nyhedsbreve eller Alle oversættelses-udvidelse meddelelser. Mange statistikker og ​​opgaver fungerer på nyhedsgruppe-basis.

Opgaverne, eller med andre ord forskellige lister over meddelelser i en nyhedsgruppe, letter forskellige brugs-tilfælde. Normalt får en oversætter en liste over alle uoversatte beskeder i en valgt nyhedsgruppe, men der er opgaver, hvor du kan gennemgå meddelelser eller bare få en liste over alle meddelelser, oversat eller ej.



Rapportering og statistik: Udvidelsen har omfattende rapporteringsfunktioner spændende fra en visning af uoversatte meddelelser på tværs af alle nyhedsgrupper i et bestemt sprog, til lister over oversættere på hvert enkelt sprog, med deres aktivitetsniveau.

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.

For more information see the tutorial How to set up a content page for translation and the in-depth documentation of the page translation feature.

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.

Use cases
You can translate almost anything with the Translate extension. Naturally there are specialized tools for translation of certain kind of texts 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.

Content translation


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.

Local interface translation in multilingual wikis
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.

Software translation
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 [Tutorial]
 * Page translation administration
 * Interface message groups (localised sidebar, main page and templates) [Tutorial]
 * [In progress] Message group management
 * [Needs updating] YAML configuration format
 * How to write YAML configuration for file based message groups [Tutorial]

Reference documents for developers

 * Installation
 * Configuration
 * [In progress] Translate explained for developers
 * Hooks
 * [In progress] Message groups
 * [In progress] File format support
 * [Unwritten] Web API
 * 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

Todo

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