Documentation
Table of Contents
Translating UI
Zabbix User Interface (UI) uses GNU gettext.
The language becomes enabled in Zabbix frontend when it is at least 50% translated.
In general, UI translations are much simpler than those for documentation, but here are some things that you have to be mindful of:
- UI translation strings often include numbered formatting markers such as %1$s, %2$s, etc. If the source string contains these markers, all of them must be included in the translation strings. Also watch for typos in these. It must be:
<percent symbol> <number> <dollar sign><”s” symbol>
- If a string needs plural forms, you will see three tabs above the translation text area. Make sure to switch between these tabs and add plural form translations.
If a string has tabs, it is important to add a translation for each tab. Otherwise, an incomplete translation will return an error during import to Zabbix and will have to be deleted.
There are also other things to look out for, but these two in particular have caused the most problems in the past.
During Zabbix release procedure translation errors are checked for, and if any are encountered, the release process cannot continue. If errors occur in a language that Zabbix team speaks, then we will attempt to fix them. Otherwise, the troublesome translations will be deleted.