Help:Extension:Translate/Page translation example/da

Velkommen! Efter at have afsluttet denne vejledning vil du vide, hvordan du opretter og administrerer sider, som kan oversættes ved brug af Translate. Vi tilstræber at holde denne vejledning så kort som mulig og samtidig introducere alle de grundlæggende begreber og opgaver. Efter at have gennemgået denne vejledning kan du bruge den uddybende dokumentation om sideoversættelses-funktionen.

There is also a set of video tutorials that parallel part of this tutorial that you can use to help learn how to use the Translate extension:

Trin 1: Før du går i gang
Denne vejledning forudsætter, at Translate-udvidelsen allerede er installeret og konfigureret. Måske har du allerede en side i tankerne, der behøver oversættelse, eller du kan bruge eksempel-siden, der er vist nedenfor, til at afprøve trinnene i denne vejledning i din egen wiki. Maybe you already have a page in mind that needs translation, or you can use the example page provided below to try out the steps in this tutorial in your own wiki.

Dette er en side, der beskriver den imaginære kommune Fréttinga.

Here is the wikicode associated to it :

Fréttinga is a small municipality in MungoLand, located on the BaMungo island. It hosts a population of about 400 people. It has some agriculture and fishing. Tourists like to visit it in the summertime. == Services == It doesn't have many services. There is a shop, and a car ferry visits the island from the mainland once a day.


 * 1. Go to the page  in your wiki (or a draft page) and click create.
 * 2. Paste the above content and save it.

Trin 2: Forberedelse
Nu har vi en side med tekst på. Hvis siden stadig bliver udsat for mange ændringer og en større omrokering, vil det være bedre at vente indtil redigeringerne minimeres til et normalt niveau, før siden tilføjes i oversættelses-systemet. Det er for at undgå alt for meget arbejde for oversætterne, da de bliver nødt til at holde trit med ændringerne.

If the page is still going to be subject to lots of changes, it may be better to wait until the edits slow down to a normal level before adding the page into the translation system. This is to avoid too much work for translators as they need to keep up with all the changes.

The page is ready for translation ? So let's see how to request translation :


 * 3. Edit
 * 4. Wrap the whole content inside  tags as shown below
 * 5. Save the page

 Fréttinga is a small municipality in MungoLand, located on the BaMungo island. It hosts a population of about 400 people. It has some agriculture and fishing. Tourists like to visit it in the summertime. == Services == It doesn't have many services. There is a shop, and a car ferry visits the island from the mainland once a day. 

You don't need to add tags to all elements.

You should never add markers like yourself; the extension does it for you in the next step.

Trin 3: Aktivering af oversættelser
Efter at have gemt siden, vil du se et link øverst på siden, der siger "Marker denne side til oversættelse" - eller "Denne side indeholder ændringer, som ikke er markeret til oversættelse." hvis du ikke er en oversættelses-administrator. Hvis du er oversættelses-administrator, klikker du på dette link. Siden bliver automatisk opdelt i fire oversættelses-enheder. Den første enhed er titlen på siden, den anden er første afsnit, den tredje er overskriften på det andet afsnit, og fjerde enhed er teksten i andet afsnit. Dette er de grundlæggende elementer på sider der kan oversættes: hver enhed er uafhængig, den kan og skal oversættes som en helhed, ændringer af side-indholdet spores til enheds-niveauet. Enheder kan omrokeres eller slettes. If you are a translation administrator, then click on the "Mark this page for translation" link. The page has been automatically split into four translation units. The first unit is the title of the page, the second is the first paragraph, the third is the header of the second paragraph, and the fourth is the text of the second paragraph. These are the basics items of translatable pages: each unit is independent; it can and must be translated as a whole; changes to the page content are tracked into the unit level. Units can be rearranged or deleted.

There is also a view of the page translation page template; this will be covered in later steps. You can give names to the translation units, but in this example, we choose to stick with the defaults.


 * 6. Click the "Mark this page for translation" link
 * 7. Ensure that the page body is split into three units correctly
 * 8. Click the "Mark this version for translation" button (reminder: you have to be a Translation administrator for this)
 * 9. Return to the page

Now you will see a new link at the top, "Translate this page", that lets translators translate the page. You might have a look at the translation tutorial which uses this page as an example and try out few translations now. Then return here for the next step.

Understanding how changes are impacting translations and translations units
Tracking changes is a very important feature, so let's make some changes and see how it works. When you open the page for editing you will see that it has been modified with markers like. These are added by the extension and help it identify which unit is which. This allows you to rearrange and edit those units. When editing the page, the markers should be left alone and their position in relation to the unit they belong to should not be changed. When moving a unit, move the unit marker, too.

When deleting a unit, delete the marker too. When adding new paragraphs, new markers will be added by the software. Do not try to do this manually, it may confuse the software. Markers you have deleted will also be automatically deleted by the bot in the existing translations.

If you do minor changes to an existing translation unit (adding a few words or a link to a paragraph), keep the marker. If you change a whole paragraph (delete and rebuilt it), delete the marker. This way, translators will have different tasks, between reviewing a fuzzy translation or create a new translation.

let's modify something !
Here is what you will do :


 * 10. Make some additions as highlighted above
 * 11. Click the "marked for translation" link at the top
 * 12. Observe the changes
 * 13. Click the "Mark for translation" button (reminder: you have to be a Translation administrator for this)
 * 14. Return to the original page

If you made translations as suggested in the previous step, you can now see those translations linked at the top of the page. You will also see that the translation is not 100 % up to date. If you go to the translation view, you see that the unit is marked as in need of updating.

Forældede oversættelser erstattes af engelsk tekst; brugeren informeres om, at oversættelsen er ufuldstændig

Oversættelses-skabelon visningen hjælper dig med at se, hvilke dele af siden er konstant i alle sprogversioner ("oversættelses-sideskabelonen", dvs. de dele som er udenfor translate-mærkerne) og viser dig også, hvis enheder er blevet flyttet rundt eller slettet.

Der kan være en lille forsinkelse før alle oversatte versioner er opdateret, fordi der kan være mange sider at opdatere.

Du har nu kender det grundlæggende, men denne vejledning vil fortsætte med flere ting, som du sandsynligvis vil støde på.

Adding an image, a category and a list with translation markers
You have a basic translatable page now, but it is very dull. Let's add an image and some other stuff to make it look more like a normal wiki page and see how those elements interact with translation.

Vi har også fjernet et afsnit, herunder dens enheds-markør, og erstattet den med en liste, så du kan se hvad der sker.


 * 15. Add an image, a category and a list to the page as shown below
 * 16. Save the page
 * 17. Click the link "marked for translation" at the top of the page
 * 18. Verify that the changes look as intended
 * 19. Click the "Mark this version for translation" button
 * 20. Return to the translatable page

Dokumenter en oversættelse
Allowing to translate only the picture title:

Or allowing to change the image file in the translated page (for localized version for example) and the title:

Her ses, at vi har sat det meste af billed-opmærkningen uden for en oversættelse enhed og har sat det i oversættelses-sideskabelonen i stedet. Dette er normalt i orden, men nogle gange ønsker oversættere måske at ændre billedet, specielt hvis det indeholder sprogligt indhold (tekst). I disse tilfælde er det normalt nemmest at omfatte hele mærkningen i en enhed (som vi gjorde for kategorien). Når oversættelsen af ​​en enhed indebærer eller interagerer med mærkning er det en god ide at skrive et lille tip til oversætterne om det. Du kan gøre dette med følgende trin. (reminder: the translation page template doesn't change between the different translated pages) This is usually okay, but sometimes translators may want to change the image, especially if it contains linguistic content (text). In those cases it's usually easiest to include the whole markup in a unit (as we did for the category).

When the translation of a unit involves or interacts with markup it's a good idea to write a small tip to the translators about it. You can do this with the following steps.


 * 21. Click "Translate this page" link at the top
 * 22. Select "qqq - Page documentation" language
 * 23. Click the message name which contains the message "A typical view of Fréttinga"
 * 24. Write "Description of an image" and click "Save"

Now, the documentation "Description of an image" is shown next to the to-be-translated-title of the image.

Om links
Tilsvarende for links er der mange måder at gøre det. Vi brugte " Special:MyLanguage/Seagull ", der automatisk omdirigerer til den oversatte version af siden, afhængigt af brugernes grænsefladesprog (hvis denne oversættelse findes). Dette er ikke en ultimativ løsning, fordi brugerne altid vil blive omdirigeret til det grænsefladesprog, de bruger, ikke til det sprog, de læser lige nu. Special:MyLanguage griber også ind i Special:Whatlinkshere og får den til ikke at fungere. Det gode ved Special:MyLanguage er, at du altid får en version af siden, selv når den ønskede oversættelse ikke findes. We used, which automatically redirects to the translated version of the page depending on the users' interface language (if that translation exists). This isn't an ultimate solution, because users will always be redirected to the interface language they are using, not to the language they are currently reading. Special:MyLanguage also interferes with Special:WhatLinksHere and makes it not work. The good thing about Special:MyLanguage is that you always get some version of the page, even if the requested translation doesn't exist.

Om kategorier
I dette eksempel er hele kategori-tildelingen en oversættelses-enhed. Dette lader oversættere ændre det til eller hvad for en navngivnings-konvention du vil bruge til kategorier. Hvis det var udenfor oversættelses-skabelonen, ville du have alle siderne Foo, Foo/da, Foo/de, Foo/ru og så videre i samme kategori. Nogle gange er det i orden, men normalt distraherer der brugerne. Sørg for, at dine oversættere ved, hvad den lokale konvention er. This lets translators change it to or whatever naming convention you want to use for categories. If it were outside the translation template, you would have all the pages Foo, Foo/de, Foo/ru, Foo/ta and so on in the same category. Sometimes this is okay, but usually it distracts the users. Make sure your translators know what the local convention is.

Om titler
To have titles considered as separated elements than text, don't forget to add a blank line (if there isn't one already) between the title and the paragraph following it.

Det følgende eksempel vil kun skabe en oversættelsesenhed:

== Services == It doesn't have many services. There is a shop, and a car ferry visits the island from the mainland once a day.

The next one will create two translation units, including one for the title.

== Services == It doesn't have many services. There is a shop, and a car ferry visits the island from the mainland once a day.

Adding a blank line allows translators to know when they can take a break. Plus it prevents issues with wikitext.

Operating on the whole page and its translations
It is also possible to move translatable pages including all their translations to a new name. Because many pages may need to be moved, this operation is not instant. You can delete either the whole page including all translations, or just one translated version of a page. You can access these functions from the same place they are on all other pages.

Managing all wiki's pages translations with Special pages
Special:PageTranslation lists all the pages in the system. Besides giving you an overview of all translatable pages, it is also possible to discourage pages from translation. This hides the page from most lists. It does not prevent further translations.

Now, you know!
Du har nu oprettet en side til oversættelse og har prøvet alle de almindelige handlinger, der kan udføres på siderne. For mere information, eller hvis du ønsker at forstå funktionen dybere, kan du fortsætte med at læse den dyberegående sideoversættelses-administration. Den indeholder også diskussion om forskellige måder at håndtere links, kategorier og skabeloner, eller fordele og ulemper ved at bruge større eller mindre oversættelses-enheder.

Going deeper?
For more information, or if you want to understand the feature more deeply, please continue reading on the in-depth documentation of page translation feature. It also contains discussion about different ways of handling links, categories and templates, or pros and cons of using larger or smaller translation units.