Help:Extension:Translate/Page translation example/es

¡Bienvenido, después de completar este tutorial sabrá cómo crear y gestionar páginas traducibles utilizando la Translate extension. Esperamos mantener este tutorial tan breve como sea posible mientras lo introduce a los conceptos y tareas básicos. Luego de completar este tutorial podrás utilizar el in-depth documentation about page translation feature.

Paso 1: Antes de iniciar
Este tutorial asume que la extensión de Traducción está instalada y configurada. Tal vez ya tenga una página en mente que necesita traducción, o puede usar la página de ejemplo de abajo para probar lo pasos en este tutorial "en su propio wiki".

Esta es una página que describe el municipio imaginario 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. Diríjase a la página Fréttinga en su wiki y haga clic en crear.
 * 2. Pegue el contenido de arriba y guarde.

Paso 2: Preparación
Ahora tenemos una página con texto. Si la página aún va a ser objeto de muchos cambios y reestructuración importante, tal vez sea mejor esperar hasta que las ediciones disminuyan a un nivel normal antes de añadir la página en el sistema de traducción. Esto es para evitar el exceso de trabajo de los traductores, ya que necesitan mantenerse al día con todos los cambios.

&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. Editar Fréttinga
 * 4. Envuelva todo el contenido dentro de &lt;translate>...&lt;/translate> las etiquetas como se muestra a continuación.
 * 5. Guarde.

Paso 3: Habilitación de traducciones
Después de guardar, verá una liga al principio de la página que dice "Marca esta página para traducción" (o "Esta página contiene cambios que no están marcados para traducción." si usted no es un administrador de traducciones). Haga clic en ese link. La página ha sido automáticamente divida en cuatro unidades de traducción. La primera unidad es el título de la página, la segunda es el primer párrafo, la tercera es el encabezado del segundo párrafo, y la cuarta es el texto del segundo párrafo. Estos son los elementos básicos de las páginas traducibles: cada unidad es independiente, pero puede y debe ser traducida en su conjunto; a los cambios en el contenido de la página se da un seguimiento en el nivel de la unidad. Las unidades pueden ser reordenadas o suprimidas.

También hay una vista de la plantilla de página de página de traducción; esto se tratará en pasos posteriores. Puede poner nombres a las unidades de traducción, pero en este ejemplo, elegimos seguir con los valores predeterminados.


 * 6. Haga clic en "Marcar esta página para traducción" enlace
 * 7. Asegúrese de que el cuerpo de la página se divide en tres unidades correctamente
 * 8. Haga clic en el botón "Marcar esta versión de la traducción"
 * 9. Regrese a la página

Ahora podrás ver un nuevo enlace en la parte superior, "Traducir esta página", que permite a los traductores traducir la página. Puede echar un vistazo a la translation tutorial, que utiliza esta página de ejemplo y probar ahora pocas traducciones. A continuación, regrese para el siguiente paso.

Paso 4: Hacer cambios
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.