Important

Traducerea este un efort al comunității, la care puteți să vă alăturați. În prezent, această pagină este tradusă 42.86%.

4. Ghidul traducerilor

This manual is aiming to help the translator. First, it explains how you can join the translation team. Then the general process of how technically a translation is done is explained. Later the translation is explained from an actual English .rst document that is translated to Dutch. Finally a summary of rules of translation is given.

Notă

Although these guidelines focus on QGIS documentation, the methods and the rules described below are also applicable to QGIS applications.

4.1. Becoming a translator

The QGIS project is always looking for people who are willing to invest some more time translating QGIS into a foreign language - even perhaps to coordinate the translation effort.

We are trying to improve our project management process and spread the load more evenly between people who each have a specific area of responsibility, so any contribution you have to make will be greatly appreciated.

If you would like to nominate yourself as a coordinator for a new language please go ahead. If more than one person nominate themselves as coordinator for the same language, please contact each other and resolve how you will manage your efforts.

4.1.1. Transifex

The web-based translating platform Transifex is used for all QGIS translations: the desktop application itself (or GUI) and the documentation. So the first thing you need is an account to login and get started.

4.1.2. Join a Project

  1. Go to https://explore.transifex.com/qgis/

  2. You can explore available projects we translate, identify their target languages with various statistics:

    • QGIS Desktop for all the pieces of text available in QGIS apps (QGIS Desktop and QGIS Server),

    • QGIS Documentation for the official LTR documentation

  3. Click on the project you would like to help translate

  4. Click on JOIN THIS PROJECT on the right side. You will be prompted to sign up.

  5. Create your account or connect using a third-party platform account. Verify your account by the link in the email you will receive.

  6. Login

  7. You then get a popup to select which language you want to help translate to. Please, note that we try to make the process as simple as possible and only mention target languages, regardless of the country parameter (e.g. French (fr) and NOT French (France) (fr_FR)). Only if there are notable differences in the languages (e.g. portuguese in Portugal vs Brazil) we may allow different versions.

    Search your target language, i.e the language you wish to help translate QGIS into, NOT necessarily all the languages you can speak:

    • If it is marked as already added then select it and press Join Project.

    • If it is not marked as already added, select it and press Request language. Keep in mind that translating an entire project will take days of work, if not weeks! Again, and sorry to repeat, it is not about selecting ALL the languages you can speak.

  8. Now you will need to wait for the language coordinator or the project maintainers to process your request. You will be notified by email when your request has been accepted. If your request has no answer for about a week, please consider writing to your language coordinator in Transifex or the QGIS Translators mailing list.

  9. You can also join any of the other QGIS projects and help everywhere too.

4.1.3. Translate

Once your request is accepted, you are able to translate any text in the project(s) you’ve chosen. Simply click on your language, select the chapter you want to translate and click on Translate. Easy, right?

In order to help you make good translation, some instructions are provided below. We strongly recommend you to read them.

Sfat

Quick access to translatable files in Transifex

If you find a wrong or missing translation in the current documentation, you can use the Translate page link in the bottom left drop-down menu of the page to reach it sources in Transifex and perform any update you wish to.

4.2. Procesul de traducere

QGIS Documentation is written in English with .rst files. In order to provide translations:

  1. A prebuild script creates translation files named .po files for the English language in the folder /QGIS-Documentation/locale/en.

  2. The sentences in the .po files are pushed to the Transifex web platform, and made available for translators who can begin to translate from English to their language with the editor.

  3. When a file is translated at 100%, the translated strings are automatically pulled back to the documentation repository, under /QGIS-Documentation/locale/<language>.

  4. At the next build of the documentation (which occurs at least once a day – see time at the bottom of the page), a script reuses the sentences to create translated output.

  5. For files not fully translated, a script pulls every two weeks translated strings from Transifex to Github and these are as well published at the next build.

  6. Whenever an .rst file is updated, the English .po file is updated and the changes are pushed to the corresponding file in Transifex. This means that when a new paragraph is added to an .rst document that was already translated, only the new/updated sentences are added to the translated .po file and needs to be translated.

Notă

Translating QGIS Desktop specificities

The main difference with translating QGIS applications is that instead of .po files, all the translatable strings in the .py, .cpp, .yaml files that shape a particular version of the application are pushed to and pulled from Transifex as a single .ts file (e.g. qgis-application/qgis_en.ts (branch release-3_30) ). Translations are pulled to Github in development branch (daily), and at release time (for every released versions).

În prezent, sunt folosite două instrumente diferite pentru a efectua traducerile QGIS:

  • The Transifex web platform, the easiest and recommended way to translate QGIS, transparently does the process described above and pulls all the translatable texts in one place for the translator. Just pick the files you want and translate. Translated files are stored in the platform until another release is pushed.

  • Qt Linguist, a Qt development tool, requires the translator to pull locally the .po (or .ts) files from the source code, translate and then push back.

Rețineți că indiferent de instrumentul ales, regulile de traducere sunt aceleași.

4.3. Traducerea unui fișier

Pentru a explica cum funcționează traducerea, vom folosi plugin-ul Heatmap ca exemplu. În acest exemplu, îl vom traduce din engleză în olandeză, dar procedeul va fi, practic, similar pentru traducerea în oricare altă limbă.

Sursa unui document se poate găsi aici:

QGIS-Documentation/source/docs/user_manual/plugins/plugins_heatmap.rst

Deci, de ce am ales acest document?

  1. It includes images, captions, headers, references and replacements.

  2. Eu l-am scris, deci este mult mai ușor pentru mine să efectuez traducerea ;-)

The build process has created the English .po file which can be found here:

QGIS-Documentation/locale/en/LC_MESSAGES/docs/user_manual/plugins/plugins_heatmap.po

The equivalent Dutch .po file (basically a copy) can be found here:

QGIS-Documentation/locale/nl/LC_MESSAGES/docs/user_manual/plugins/plugins_heatmap.po

Along this file you will see a tiny .mo file which indicates that it does not hold any translations yet.

4.3.1. Traducerea pe Transifex

In order to translate using Transifex, you need to:

  1. create an account on Transifex and join the QGIS project.

  2. Once you are part of a language team, click on the corresponding project (in this case QGIS Documentation). A list of available languages with their ratio of translation is displayed.

    ../../_images/transifex_choose_language.png

    Fig. 4.22 Select language for translation in the Transifex menu

  3. Hover over your language and click either:

    • View resources: translatable .po files with their ratio of translation, number of strings and some more metadata are now displayed.

    • or Translate: opens the interface of translation with all the available .po files

  4. Identify the file you’d like to translate (in our case we are looking for the docs_user-manual_plugins_plugins-heatmap, the heatmap plugin file) or any unfinished file and click on it: strings in the files are loaded and you can use the interface to filter, translate, suggest translation…

    Sfat

    Clicking the Translate page link in the bottom left drop-down menu of a page brings you directly to its corresponding translation page in Transifex.

  5. All you need to do is select each text and translate following the guidelines.

For further information on the use of Transifex Web Editor, see https://help.transifex.com/en/articles/6318216-translating-with-the-web-editor.

4.3.2. Traducere în Qt Linguist

With Qt Linguist, you need to:

  1. manually grab the .po or .ts file(s). This can be achieved by downloading the file(s) either from Transifex platform or from the locale/$language folder of the source repository (in GitHub),

  2. proceed to the translation locally

  3. upload the modified files to their sources (Transifex or GitHub).

While downloading and uploading translatable files can be done with Transifex, it’s not advised to use this process. Since there’s no versioning system on Transifex, the file you upload will simply replace the existing one and potentially overwrite any modification made by others on the platform in the meantime.

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

../../_images/linguist_choose_language.png

Fig. 4.23 Selectați limba pentru traducere în meniul linguist

Limba Țintă trebuie să fie completată corect. Limba Sursă poate fi lăsată așa cum este, cu limba POSIX și Țara/Regiunea pe Orice Țară.

When you press the OK button Qt Linguist is filled with sentences and you can start translating, see Fig. 4.24.

../../_images/linguist_menu.png

Fig. 4.24 Traducerea cu ajutorul meniului Linguist

În meniu veți vedea următoarele butoane, ușor de utilizat.

  • linguist_done_next Butonul Translation Done Next este cel mai important. Dacă elementul are nevoie de traducere, introduceți o traducere în câmpul de text, apoi apăsați acest buton. Dacă elementul nu necesită traducere, lăsați gol câmpul de text și apăsați, de asemenea, acest buton, care indică faptul că elementul este în regulă, continuându-se cu următorul.

  • linguist_previous Butonul Goto Previous, poate fi folosit pentru a merge la elementul tradus anterior.

  • linguist_next Butonul Goto Next, poate fi folosit pentru a merge la următorul element de tradus.

  • linguist_next_todo Butonul Next Todo, efectuează saltul la prima traducere care necesită o traducere. Este foarte util atunci când documentul original s-a schimbat și numai câteva expresii noi/modificate trebuie să fie traduse.

  • linguist_previous_todo Butonul Previous Todo, caută înapoi și sare la primul element de traducere care necesită o traducere.

For further information on the use of Qt Linguist, see https://doc.qt.io/qt-5/linguist-translators.html

Atenționare

If you want to download content to translate from the source repository, never do this in the master branch. For translations there are always translation branches available, once a document is fully updated in English for a certain version. As an example, to translate the manual of QGIS 2.8, you have to use the manual_en_v2.8 branch.

4.3.3. Traduceți un manual

Acum vom începe traducerea manualului pentru pluginul_heatmap!

Traducerea celor mai multe propoziții ar trebui să fie simplă. Pe durata acestei sesiuni de traducere, vom sublinia părțile (expresiile rst) care necesită traducere.

Mai jos, vedem o propoziție de tradus, mai interesantă:

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.

Această frază conține două declarații rst:

  1. |heatmap| cuvintele dintre | sunt înlocuiri și nu ar trebui să fie traduse niciodată! Acesta, de exemplu, va fi înlocuit de pictograma plugin-ului Heatmap!

  2. :sup:`Heatmap`, expresia :sup: este o declarație de superpoziție, care imprimă textul următor, un pic mărit. Se folosește pentru a prezenta textele într-un balon, care apare la trecerea pe deasupra elementului din bara de instrumente, el putând arăta în mod diferit dacă a fost tradus în aplicația QGIS. În cazul limbii olandaeze, nu a fost tradus!

Toate celelalte texte simple din această propoziție pot fi traduse!

Următorul element de tradus conține expresia :ref:, care este frecvent folosită pentru a face trimitere la o altă secțiune a manualului respectiv! Textul urmat de expresia :ref: nu ar trebui să fie schimbat, pentru că acesta reprezintă un identificator unic!

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 hyperlink. When the header this reference is referring to is translated, all references to this header will be automatically translated as well.

Articolul următor conține eticheta rst :menuselection: urmat de textul afișat, în mod curent, într-un meniu din aplicația QGIS, acesta putând fi tradus în cerere și, prin urmare, ar trebui să fie schimbat atunci când este cazul.

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

La punctul de mai sus „View –>”este, de fapt, tradus ca „Beeld –>”, aceasta fiind traducerea olandeză utilizată din aplicația QGIS.

Un pic mai departe vom întâlni următoarele elemente greu de tradus:

The |heatmap| :sup:`Heatmap` tool button starts the Dialog of the Heatmap
plugin (see :numref:`figure_heatmap_settings`).

It holds a reference to a figure figure_heatmap_settings_, and like a reference to a section this reference should not be changed!! The reference definition 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_settings. When a PDF document is created figure_heatmap_settings_ is replaced with a figure number.

Următorul element de traducere cu atribute rst este următorul:

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

Nu eliminați steluțele din linia de mai sus. Textul conținut între ele va fi transcris îngroșat. Adesea, textul este inclus chiar în dialog și poate fi, la fel de bine, tradus în aplicație.

Următoarea traducere conține eticheta rst :guilabel:.

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

Textul Avansat al etichetei poate fi tradus din aplicația QGIS și, probabil, chiar trebuie tradus!

Următorul element de tradus conține ``airports``. Apostrofurile sunt folosite pentru a atribui textului un alt font. În acest caz, este vorba de o valoare literală și nu are nevoie de traducere.

For the following example, we will use the ``airports`` vector point
layer from the QGIS sample dataset (see :ref:`label_sampledata`).
Another excellent QGIS tutorial on making heatmaps can be found on
`https://www.qgistutorials.com
<https://www.qgistutorials.com/en/docs/creating_heatmaps.html>`_.

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

4.3.4. Sumarul regulior pentru traducere

  1. Nu schimbați textul dintre două caractere |, cum ar fi |bronze|, |checkbox|, |labels|, |selectString|, |addLayer| … Acestea sunt etichete speciale, folosite pentru a substitui imaginile

  2. Do not change references that start with roles like :ref:, :file:, :numref: unless they include a title. In that case, you can translate the title but keep unchanged the link (i.e., the text between < and >)

    Sfat

    When a title is provided for a reference, Transifex may display a number in the English source text in replacement of the link part. Click on the number in the source text to add the reference link next to the title being translated.

  3. Nu schimbați referințe care se termină cu liniuțe de subliniere ca figure_labels_1_

  4. Nu modificați adresa hiperlegăturilor, însă puteți modifica descrierea lor externă. Lăsați neatinsă liniuța de subliniere de la sfârșit, neintroducând spațieri adiționale (>`_)

  5. Schimbați textul dintre ghilimele, care urmează după etichetele :sup:, :guilabel: și :menuselection:. Verificați dacă/cum sunt traduse în aplicația QGIS. Nu schimbați denumirea etichetelor.

  6. Textul inclus între steluțe duble și apostrofuri duble indică adesea valori sau nume de câmpuri, uneori necesitând traducere, alteori nu.

  7. Aveți grijă să utilizați exact același (număr de) caractere speciale, cum ar fi `, ``, *, **, ::, similar textului sursă, . Acestea contribuie la cosmetizarea informațiilor furnizate

  8. Nu puneți un spațiu, înainte sau după textul inclus între caractere speciale sau din cadrul etichetelor

  9. Nu încheiați șirurile traduse cu un nou paragraf, în caz contrar, textul nu va fi tradus pe durata generării codului html.

Respectați regulile de mai sus iar documentul tradus va arăta foarte bine!

Pentru orice întrebare, vă rugăm să contactați Echipa Comunității QGIS sau Echipa de Traducere QGIS.