Help:Extension:Translate/Page translation example/ru

Добро пожаловать! После прохождения этого обучения вы узнаете, как создавать и управлять страницами для перевода используя Раширение для переводов. Мы старались сделать это обучение как можно более коротким, показав при этом все основные концепции и шаги. После обучения вы сможете воспользоваться более подробной документацией о возможностях перевода страниц.

Шаг 1: Перед началом
Этот туториал предполагает, что Расширение для переводов уже установлено и настроено. Может быть вы уже припоминаете какую-либо статьюб которую неплохо было бы перевести на другие языки, или вы можете использовать тренировочную страницу представленную ниже для отработки шагов на своей собственной Вики.

Эта страница описывает воображаемый муниципалитет 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. Перейдите на страницу Fréttinga в своей вики нажмите кнопку создания страницы.
 * 2. Поместите в поле редактирования вышележащий текст и сохраните страницу.

Шаг 2: Подготовка
Теперь у нас есть страница с каким-то текстом. Если страница всё ещё часто подвергается изменениям, стоит дождаться, когда изменения замедляться до нормального уровня и только тогда добавить её в систему переводов. Это следует иметь в виду для того чтобы снизить нагрузку на переводчиков, поскольку им придётся переводить все изменения.

&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. Отредактируйте Fréttinga
 * 4. Перетащите всё содержимое в &lt;translate>...&lt;/translate> тэги, как показано ниже
 * 5. Сохраните страницу

Шаг 3: Включение переводов
После сохранения страницы, вы увидите ссылку на верху страницы, гласящую "Пометьте эту страницу для перевода" (или "Эта страница содержит изменения, которые не были помечены для перевода." если вы не администратор перевода). Нажмите на эту ссылку. Страница автоматически разобьётся на 4 блока перевода. Первый — заголовок страницы, второй — это первый абзац, третий — это заголовок второго абзаца, и четвёртый — это текст второго абзаца. Это базовые правила переводимых статей: каждый блок независим; он должен переводиться целиком; изменения на странице требуют обновления всего блока. Блоки можно изменять и удалять.

Также существует просмотр шаблона страницы; об этом будет рассказано в следующих шагах. Вы можете давать названия блокам перевода, но в этом примере мы решили оставить установки по умолчанию.


 * 6. Нажмите ссылку "Пометить страницу для перевода"
 * 7. Удостоверьтесь, что страница разбита на три блока правильно
 * 8. Нажмите кнопку "Пометить эту версию для перевода"
 * 9. Вернитесь на страницу

Теперь вы увидите новую ссылку "Переведите эту страницу" наверху, которая позволяет переводчикам работать с этой страницей. Вам стоит взглянуть на обучение переводу которое использует эту страницу как пример и попробовать написать несколько переводов. Затем вернитесь обратно сюда для продолжения урока.

Шаг 4: Внесение изменений
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 are replaced with the English text. 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.

Шаг 5: Добавление других вики-элементов
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.

Заключение
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.