See for the official Zabbix site.

Translating Zabbix

Jump to: navigation, search

Translating Zabbix

It is possible to participate in translation of Zabbix interface and documentation. It is actually very much appreciated - native speakers are in the best position to create quality translations.

Translation status and maintainers

If you want to help with translation, it's best to coordinate the efforts. The following table lists language maintainers. If there is an existing maintainer, feel free to contact them for advice or to report problems with that particular translation. If there's no maintainer for your language, feel free to add it - and yourself as the maintainer, if you would like to participate.

Translation status shows whether a translation is show by default. Translations that are not shown really need help - join in!

If a translation drops below 75% completion, it is hidden from the language selection. Note that it is not removed, just not displayed in the default dropdown. A translation is added to the dropdown when it reaches 100% completion.

User links in the table may go to your Zabbix forum user page, or user page on this wiki.

Links to the forum user page should follow a syntax like this (replace <user_ID> and <User name>):

 [<user_ID> <User name>]

Links to the user page on this wiki should follow a syntax like this (replace <login_name> and <User name>):

 [[User:<login_name>|<User name>]]
Language Language code Translation visible Valid maintainers (all versions)
3.0 4.0 trunk
Bulgarian bg No No No mystical
Catalan ca No No No Martí Cardús
Chinese (China) zh_CN Yes Yes Yes WangYuying (Wayne Wang), Jack.lee, Darkyyx - 雨云溪, Yi Lu - 陆逸
Chinese (Taiwan) zh_TW No No No Lhy719
Czech cz Yes Yes Yes malyl, martinds
Dutch nl No No No open-future, acropia
English (United States) en_US Yes Yes Yes Zalex_UA
Finnish fi No No No Ekakela
French fr Yes Yes Yes Antonin, Sébastien Maccagnoni-Munch (tiramiseb),C. Triomphe, Daudet
Georgian ka No No No George Machitidze (giomac)
German de No No No Volker Fröhlich (volter), Florian Koch (flo), Jens Berthold (maxhq), Timo (Sugarman), Max Kubiak (mighty_oak), Joachim Schwender
Greek el No No No giannis
Hebrew he No Yes Yes Yaron
Hungarian hu No No No szenrobi
Indonesian id No No No busel7
Italian it Yes Yes Yes quadrata (Dimitri Bellini)
Japanese jp Yes Yes Yes Kodai, Atsushi
Korean ko Yes Yes Yes Harper Park (righ) JK Kim
Latvian lv No No No
Lithuanian lt No No No
Norwegian nb No No No eirik333, Bård
Persian fa No No No Mohammad Sharifi (Starless boi), mohammad shahrokhi
Polish pl Yes Yes Yes refaston, Paweł Jarosz (zaicnupagadi), daftu, pawelsel, User:mikolaj9521, User:Nolaan
Portuguese (Brazil) pt_BR Yes Yes Yes Adail Horst (spaww), Rafael Fontenelle, Raul Libório
Portuguese (Portugal) pt_PT Yes Yes Yes User:Hugosantos
Romanian ro No No No User:Link01
Russian ru Yes Yes Yes DotNeft, Neogan
Slovak sk Yes Yes Yes Jan Garaj
Spanish es No No No saulortega, Óscar García, Jesús Moreno, Rafael Amador
Swedish sv No No No User:Ngyori
Turkish tr Yes Yes Yes maidis,nakof
Ukrainian uk Yes Yes Yes Zalex_UA, Heilig
Vietnamese vi No No No Quang Nguyễn Huyền (quangnh), tvtrung, Đào Nguyễn Anh (nadao), Travis Tran

Mailing list

Zabbix translators mailing list is available.

Objects to translate

There are two possible things to translate at this point:

Translating frontend

If you want to translate Zabbix frontend:

  1. register on this wiki
  2. log into Pootle using the same username and password you registered with in the previous step
  3. subscribe to the translator mailing list
  4. add yourself to the maintainer table above
  5. have a look at your language specific translation page
    • it's linked to the language name in the maintainer table above (if there is one)

You will also need permissions to submit translations. Easiest way to obtain them is to ask in the #zabbix IRC channel on Freenode and provide your Pootle login. Try to ping "zalex" user. Another way is to send email to support @

If there are existing translators for your language, make sure to contact them - maybe there is an established workflow already, or some language-specific rules that should be followed.

Syncing translation with GIT

Two ways synchronization Pootle <-> GIT is performed automatically each day. This way it's assured that all translation from Pootle are included. Internal instructions are here.

Testing translation

If you want to use finished PO file, which is not synced to SVN yet, - you can download it from Pootle, put it in zabbix frontend corresponding folder, run and you should see all strings translated. Example:

 # yum install -y gettext || apt-get install -y gettext
 # cd /usr/local/src/zabbix/frontends/php || cd /usr/share/zabbix/
 # cd locale/sk/LC_MESSAGES/
 # rm -rf frontend.po && wget
 # cd ../../..
 # restart your web server

Translating manual

If you want to translate the manual, contact Zabbix developers at, providing your forum username and language you want to translate manual to.

Note that it is suggested to completely finish frontend translation before considering the manual - translating the manual is a much bigger amount of work.

Creating translation
  • If you create a new Zabbix manual translation, you should immediately create a complete tree structure of the whole manual. This is crucial, as otherwise users are likely to miss parts of manual that have not been yet translated.
  • Create manual pages so that the link name is absolutely identical to the English, except for two letter country code at the start of the link. Check that the selector of language at the top of the page works properly.
  • For all initially created pages, add at the top of page a warning like this, and edit the link for the correct path for each page (source code):

<note important> This page has not yet been translated. See the original page.</note>

Remove this warning only after translation of that page is completed.

Working on the translation
  • Try to translate the entire page and then proceed to the next.
  • Try to commit larger parts of the page, i.e. don't save small changes very often. To save the work done, use the "Preview" button. When you click on "Preview" page is stored on the server as a draft, and you can edit it later. During this period, other users will not see the changes already made. If the page has a draft saved, viewing it instead of "Edit this page", "Edit Draft" button will be displayed. Once you click "Edit Draft", make sure to choose "Recover Draft" to continue editing from the previous point.
  • Use the field "Edit summary" and mark "Minor Changes" if appropriate. Always populate "Edit summary" field. Remember, checking "Minor Changes" will prevent users who had subscribed to the page changes from receiving the notification. In the revision history (accessed by "Old revisions" link on each page) such minor changes are shown in italics. It is recommended to use "Minor Changes" option only when correcting typos.
  • If you update documentation translation and original changes were accompanied by a comment, repeat that comment in your own edit summary.
  • If you translate some changes, translate them fully - for example, do not skip a paragraph that might be difficult to translate. In the worst case scenario, replicate the English version and consult other translators.
  • Try to re-create contents of the English version in the screenshot - including hosts, host groups, items etc. Also try to replicate size, viewport and cropping of original screenshots.
  • When translating the documentation, follow the same concepts as used in the frontend translation. Do not use English if the frontend has that word translated.