Інструкції для перекладачів¶

First translation¶

To create documentation first rst documents are created. A prebuild script creates translation files named .po files for the english language in the folder /QGIS-Documentation/i18n/en.

Ці «оригінали» копіюються у каталоги інших мов.

The sentences in the .po files needs to be translated from english to the language with a translation tool editor. There is a web translation tool called pootle we would like to use, but it is not activated yet. However there is an excellent tool supplied with the qt development tools named Qt Linguist.

When you want to contribute, first get a .po file and add translations for the sentences in the .po file.

When you are finished the .po file is placed back in the right place and during the next build the buildscript now creates .mo files next to the .po files.

These .mo files are actually used by the script to create translated output.

Update translations¶

When afterwards an rst document is updated a new .po file is created in the english part. The contents of this new file will be merged with already existing .po files for each language. This means that when a new line is added to an rst document that was allready translated, only the new/updated sentences are added in the translated .po file and needs to be translated. The amount of work for updating translations for next versions of QGIS should be relative small.

Переклад у Qt Linguist¶

When you open the .po file in Qt Linguist for the first time you will see the following dialog:

Figure Translation 1:

Вибір мови перекладу в Qt Linguist

Вкажіть мову перекладу в полі «Target language». Поля «Source language» та «Country/Region» можна не чіпати.

When you press the [OK] button Qt Linguist is filled with sentences and you can start translating, see Figure translation 2.

Figure Translation 2:

Translate using the linguist menu

На панелі інструментів знаходяться кнопки, що значно полегшують роботу.

• The Translation Done Next button, is the most important button. If the item needs translation, you enter a translation in the text field, then hit this button. If the item does not translation just leave the text field for translation empty and also hit this button which indicates the item is done and you continue with the next item.

• Перейти до попереднього рядка.

• Перейти до наступного рядка.

• Наступний неперекладений рядок — перейти до першого неперекладеного рядка. Корисно, коли документ був оновлений і потрібно перекласти лише нові рядки.

• Попередній неперекладений рядок. Виконує пошук у зворотньому напрямі та переходить до першого знайденого неперекладеного рядка.

Переклад посібника користувача¶

Почнемо переклад файлу plugin_heatmap.

The first two items do not need translation, just push the toolbar button which considers the translation finished and jump to the next item.

When I get to the third item we see a more interesting sentence to translate:

The |heatmap| :sup:`Heatmap` plugin allows to create a heatmap from a point vector map. A heatmap is a raster map showing the density or magnitude of point related information. From the result "hotspots" can easily be identified.

У ньому знаходиться дві конструкції RST:

1. |heatmap|. Слова розміщені між | є підстановкою і ніколи не перекладаються! Ця конструкція буде замінена на іконку модуля «Теплокарта».

2. :sup:`Heatmap` `` the ``:sup: statement is a superposition statement and prints the following text a bit higher. This is used to show the popup texts that appear when you hover above the toolbar item and this may be different when it is actually translated in the QGIS application. In this case it is not!

Весь інший текст у цьому рядку можна перекладати на свій розсуд.

The fifth translation item contains the :ref: rst statement that is commonly used to refer to another section somewhere in het manual! The text following a :ref: statement should never be changed because it is a unique identifier!

First this core plugin needs to be activated using the Plugin Manager (see Section :ref:`load_core_plugin`). After activation the heatmap icon |heatmap| can be found in the Raster Toolbar.

In this case “load_core_plugin” is a unique reference identifier placed before an rst item that has a caption. The ref statement will be replaced with the text of the header and turned into a hyerlink. When the header this reference is refering to is translated, all references to this header will be automatically translated as well.

Наступний рядок містить елемент :menuselection:, за яким знаходиться власне назва пунктів меню. Ця назва перекладається так само, як вона перекладена в інтерфейсі QGIS.

Select from menu :menuselection:`View -->` :menuselection:`Toolbars -->` :menuselection:`Raster` to activate the Raster Toolbar when it is not yet activated.

У нашому випадку елемент “View –>” буде перекладено як “Beeld –>”, оскільки саме так називається цей пункт меню в голландській локалізації QGIS.

Трохи пізніше нам зустрінеться такий блок тексту:

The |heatmap| :sup:`Heatmap` toolbutton starts the Dialog of the Heatmap plugin (see figure_heatmap_2_).

It holds a reference to a figure figure_heatmap_2_, and like a reference to section this reference should not be changed!! The reference definition itself from the rst-document is not included in the .po file and can therefore not be changed. This means the reference to figures can not be translated. When HTML is created you will see figure_heatmap_2. When a PDF document is created figure_heatmap_2_ is replaced with a figure number.

Наступний текстовий блок містить декілька елементів форматування:

**Input Point dialog**: Provides a selection of loaded point vector maps.

Do not remove the stars in above line. It will print the text it holds in bold. The text itself is often text included in the dialog itself and may wel be translated in the application.

Наступний блок містить елемент розмітки :guilabel:.

When the |checkbox| :guilabel:`Advanced` checkbox is checked it will give acces to additional advanced options.

The text Advanced of the guilabel tag may wel be translated in the QGIS application and probably needs to be changed!

The following translation item contains ``airports``. The apostrophs are used this to give text another textfont. In this case it is a literal value and does not need translation.

For the following example, we will use the ``airports`` vector point layer from the QGIS sample dataset (see :ref:`label_sampledata`). Another exellent QGIS tutorial on making heatmaps can be found on `http://qgis.spatialthoughts.com <http://qgis.spatialthoughts.com/2012/07/tutorial-making-heatmaps-using-qgis-and.html>`_.

This item also includes a hyperlink with a url and an external presentation. The url should ofcourse be left intact, you are allowed to change the external text “http://qgis.spatialthoughts.com” which is visible by the reader. Never remove the underscore at the end of the hyperlink which forms an essential part of it!!

Основні правила¶

1. Do not change replacements like |nix|
2. Do not change references that start with the tag :ref:
3. Do not change references that end with an underscore like figure_1_
4. Do not change the url in hyperlinks, but you may change the external description. Leave the underscore at the end of the hyperlink
5. Change the contents of :sup:, :guilabel: and :menuselection:, Check if/how it is translated in the QGIS Application.
6. Text between Double Stars and double apostrophes often indicate values or fieldnames, sometimes they need translation sometimes not.
7. Be aware to use exactly the same apostrophes of the source text.
8. Don’t end the translated strings with a new paragraph, otherwise the text will not be translated during the html generation.

Керуйтеся цими простими правилами і ваш переклад буде гарним!