Help:Extension:Translate/Page translation example/nb

Velkommen! Etter å ha gått gjennom denne veiledningen vil du vite hvordan man oppretter og vedlikeholder oversettbare sider med Translate-utvidelsen. Vi ønsker å holde denne veiledningen så kort som mulig, mens vi samtidig introduserer alle de grunnleggende ideene og oppgavene. Etter at du har gått gjennom denne veiledningen kan du gå videre til den grundigere dokumentasjonen av Translate-funksjonene. We aim to keep this tutorial as short as possible, while introducing all the basic concepts and tasks. After completing this tutorial you can use the in-depth documentation about page translation feature.

Første steg: Før du begynner
Denne veiledningen går ut fra at Translate-utvidelsen allerede er installert og konfigurert. Kanskje har du allerede ei side som trenger oversettelse, ellers kan du bruke eksempelsida som vises nedenfor for å fullføre stegene i denne veiledningen på 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.

Please note : Consequently, we will consider that you are a Translation administrator on your wiki (...if you can, you should declare yourself now !), otherwise you may not access to some of the links/pages described here.

Let's go!

Dette er ei side som beskriver den fiktive kommunen 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. Gå til sida Fréttinga på wikien din (eller en kladdeside) og klikk opprett.
 * 2. Lim inn innholdet ovenfor og lagre det.

Andre steg: Forberedelse
Nå har vi ei side med noe tekst. Om sida fortsatt kommer til å gjennomgå mange endringer kan det være bedre å vente med å merke den for oversettelse til den har stabilisert seg. Dette er for å unngå for mye jobb for oversettere, siden de vil måtte holde tritt med alle endringene.

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. Rediger Fréttinga
 * 4. Pakk inn hele innholdet i &lt;translate>…&lt;/translate> -tagger, som vist nedenfor
 * 5. Lagre sida

 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. 

Merk at du ikke må legge til &lty;translate>-tagger til alle elementer, eller legge til markører som.

Tredje steg: Slå på oversettelser
Etter at du har lagra sida vil du se ei lenke på toppen hvor det står «Merk denne siden for oversettelse», eller «Denne siden inneholder endringer som ikke er merket for oversettelse» dersom du ikke er oversettelsesadministrator. Hvis du er oversettelsesadministrator, klikk på lenka «Merk denne siden for oversettelse». Siden har automatisk blitt delt inn i fire oversettelsesenheter. Den første enheten er tittelen på siden, den andre er første avsnitt, den tredje er overskriften til andre avsnitt, og den fjerde er andre avsnitt. Dette er de grunnleggende enhetene på oversettbare sider: hver enhet er uavhengig; den kan og å oversettes i sin helhet; endringer til sideinnholdet spores på enhetsnivå. Enheter kan flyttes på 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.

Det er også en visning av sidemalen til sideoversettelsen; dette vil dekkes i senere steg. Du kan gi navn til oversettelsesenhetene, men i dette eksempelet holder vi oss til standardvalgene.

(reminder: you have to be a Translation administrator for this)
 * 6. Klikk lenka «Merk denne siden for oversettelse»
 * 7. Sørg for at sidens innhold er delt inn i tre enheter på riktig måte
 * 8. Klikk knappen «Merk denne versjonen for oversettelse»
 * 9. Returner til siden
 * 9. Return to the page

Nå vil du se ei ny lenke på toppen «Oversett denne siden», som lar oversettere oversette siden. Du vil kanskje ønske å sjekke ut oversettelsesveiledningen som bruker denne siden som et eksempel og prøve ut noen oversettelser nå. Kom så tilbake hit for neste steg.

Understanding how changes are impacting translations and translations units
Sporing av endringer er en veldig viktig funksjon, så la oss gjøre noen endringer og se hvordan det funker. Når du åpner sida for redigering vil du se at den har fått markører som. Disse legges til av utvidelsen for å hjelpe til å identifisere hvilken enhet som er hva. Dette lar deg flytte på og redigere disse enhetene. Når du redigerer sida bør markørene få være som de er, og posisjonen bør ikke endres i forhold til enheten de hører til. Når du flytter en enhet, flytt markøren også. 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.

Når du sletter en enhet, slett markøren også. Når du legger til nye avsnitt vil nye markører legges til av programvaren. Ikke prøv å gjøre dette manuelt, siden det kan forvirre programvaren. Markører du har sletta vil også slettes av botten i de eksisterende oversettelsene.

Om du gjør mindre endringer i en oversettelsesenhet (f.eks. legger til noen få ord eller legger til ei lenke), behold markøren. Om du endrer et helt avsnitt (sletter det og starter på nytt), slett markøren. På denne måten vil oppgaven for oversetterne være forskjellig, enten fikse noen småting eller oversette et nytt avsnitt.

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

(reminder: you have to be a Translation administrator for this)
 * 10. Legg til noe, som vist ovenfor
 * 11. Klikk på lenka «merket for oversettelse» på toppen
 * 12. Sjekk endringene
 * 13. Klikk på knappen «Merk for oversettelse»
 * 14. Returner til originalsida
 * 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.

Utdaterte oversettelser erstattes av tekst på engelsk; brukeren blir fortalt at oversettelsen er ufullstendig.

The translation template view helps you to see what parts of the page are constant in all language versions (the "translation page template", i.e. the parts outside translate tags) and also shows you if units have been moved around or deleted.

There might be a slight delay before all translated versions are updated, because there can be many pages to update.

You now know the basics, but this tutorial will continue with more things that you are likely to encounter.

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.

We also removed a paragraph, including its unit marker, and replaced it with a list, so you can see what happens.


 * 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

Document a translation
Here you can see that we left most of the image markup outside of a translation unit and have it in the translation page template instead. (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.

About links
Similarly, for links there are many ways to do it. We used " Special:MyLanguage/Seagull ", 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.

About categories
In this example, the whole category assignment is a translation unit. 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.

About titles
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.

The following example will only create one translation unit:

== 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 !
You have now created a translatable page and tried all of the common actions that can be performed on translatable pages.

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.