Help:Extension:Translate/Page translation example/fr

Bienvenue ! Une fois ce tutoriel achevé, vous saurez comment créer et gérer les pages traduisibles en utilisant l'extension Translate (Traduire). Nous souhaitons garder ce tutoriel aussi concis que possible, bien qu'il présente tous les concepts et tâches de base. Après avoir achevé ce tutoriel, vous pouvez voir la documentation plus approfondie concernant l'outil de traduction de page.

Étape n°1 : Avant de commencer
Ce tutoriel suppose que l'extension Translate est déjà installée et configurée. Peut-être avez-vous déjà en tête une page qui nécessite une traduction sinon vous pouvez utiliser la page d'exemple disponible ci-dessous pour exécuter les étapes de ce tutoriel dans votre propre wiki.

Voici une page décrivant la municipalité imaginaire de Fréttinga. 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 summer time. == Services == It doesn't have many services. There is a shop and car ferry visits the island from mainland once a day.
 * 1. Allez sur la page Fréttinga dans votre wiki et cliquer sur créer.
 * 2. Collez le contenu ci-dessus et publiez-le.

Étape n°2 : Préparation
Maintenant, nous disposons d'une page avec un texte. Si la page est toujours sujette à de multiples modifications et remises en forme majeures, il est peut-être préférable d'attendre que le nombre de modifications diminue jusqu'à un niveau acceptable avant d'ajouter la page dans le système de traduction, ceci afin d'éviter une surcharge de travail pour les traducteurs qui devront mettre à jour toutes les modifications apportées.

&lt;translate> 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 summer time. == Services == It doesn't have many services. There is a shop and car ferry visits the island from mainland once a day. &lt;/translate>
 * 3. Modifiez Fréttinga
 * 4. Insérez tout le contenu dans les balises ... comme affiché ci-dessous
 * 5. Publiez la page

Étape n°3 : Activation des traductions
Après avoir publié la page, vous verrez un lien en haut de la page disant "Mark this page for translation" (Marquer cette page pour traduction) ou bien "This page contains changes which are not marked for translation" (Cette page contient des modifications qui n'ont pas été marquées pour traduction) si vous n'êtes pas un administrateur traductions. Cliquez sur ce lien. La page est automatiquement divisée en quatre unités de traduction. La première unité est le titre de la page, la seconde est le premier paragraphe, la troisième est l'entête du second paragraphe et enfin, la quatrième est le texte du second paragraphe. Il s'agit des items de base des pages traduisibles : chaque unité est indépendante. Elle peut et doit être traduite dans son ensemble. Les modifications peuvent être réarrangées ou supprimées.

Il y a aussi une visualisation de la page de traduction dans la page modèle ; ce point sera vu dans les dernières étapes. Vous pouvez donner des noms aux unités de traduction, mais dans cet exemple, nous choisissons de garder ce qu'il y a par défaut.


 * 6. Cliquez sur le lien "Mark this page for translation" (Marquer cette page pour traduction)
 * 7. Assurez-vous que le corps de page est bien divisé correctement en trois unités
 * 8. Cliquez sur le bouton "Mark this version for translation" (Marquer cette version pour traduction)
 * 9. Revenez sur la page

Maintenant, vous verrez un nouveau lien en haut de page, "Translate this page" (Traduire cette page) qui vont permettre aux traducteurs de traduire la page. Vous pouvez jeter un coup d'œil sur le tutoriel de traduction qui utilise cette page comme exemple et tentez de faire quelques traductions dès maintenant.

Step 4: Making changes
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. &lt;languages /> &lt;translate> &lt;!--T:1--> 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 summer time. It has marvelous beaches with a lot of seagulls. == Services == &lt;!--T:2--> &lt;!--T:3--> It doesn't have many services. There is a shop and car ferry visits the island from mainland once a day. In 2009 January the roof of the church in the island fell down. It was rebuilt collaboratively in the following summer. &lt;/translate>


 * 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
 * 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 look at the translated version, you will see the new paragraph in English, and the changed paragraphs will be highlighted (see screenshot). If you go to the translation view, you see that the unit is marked as in need of updating.

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.

Step 5: Adding other wiki elements
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.

&lt;languages /> &lt;translate> &lt;!--T:1--> 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 and tourists like to visit it in the summer time. It has marvelous beaches with a lot of seagulls. == Services == &lt;!--T:2--> &lt;!--T:3--> It doesn't have many services. There is a shop and a car ferry visits the island from the mainland once a day. Main events: * The roof of the church fell down in 2009 * New church was built in 1877 &lt;/translate>
 * 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

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. 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"

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.

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're 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.

Last words
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.

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.

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