1.34. How to improve translation

NextGIS Web is an open solution, which can be improved by any user. The following user interface languages are currently available for NGW:

  • Bulgarian

  • Czech

  • Deutsch

  • English

  • Spanish

  • French

  • Italian

  • Portuguese

  • Russian

  • And Chinese

We invite users to contribute to the quality of our translations. If you are an expert in any of the listed or other languages, you can improve the current user interface by yourself. As soon as 80% of translated content appears, we add a new language to NGW.


Pic. 1.132. NextGIS Web GUI project for user interface translation

1.34.1. Join the project

The translation of NextGIS Web is carried out on the platform POEditor. First, you need to sign up. After authentication you can join the NextGIS Web GUI project via this link. Then select languages and click Join translation. After that, this page will display a list of projects (in our case, NextGIS Web GUI) that have a set of selected languages.


Pic. 1.133. Selecting a language for translation

1.34.2. How to translate

To start translating click on the icon of a specific language in the project. Row order and filter are customizable. There is also a search.


Pic. 1.134. Translator UI window

Strings often contain such parameter names as ‘date_first’ and ‘date_last’ like in the image above. They don’t need to be translated.

Russian translation example:

  • en. - ‘date_first’ and ‘date_last’ are mutually exclusive.

  • ru. - ‘date_first’ и ‘date_last’ взаимоисключающие.

Also you can see these parameters: %s, %d, %f and like these that also don’t require the translation. When the program is running, they are automatically replaced by string or numeric parameters.

Example 1:

  • en. - User count: %d.

  • ru. - Количество пользователей: %d.

Example 2:

  • en. - Field ‘%s(?)’ encoding is broken.

  • ru. - Кодировка поля ‘%s(?)’ повреждена.

Parameters are often enclosed in single quotes ‘, double quotes ” or brackets (). Such diversity does not make much sense and is explained by the lack of agreement among developers on formatting. Leave it in the translation as in the original raw.