ZABBIX BUGS AND ISSUES

Impossible to correctly translate some parts of Zabbix

Details

  • Zabbix ID:
    NA

Description

I'm currently trying to improve the french translation, and I'm starting to understand why some strings are not correctly translatable. Zabbix front-end sentences are sometimes defined as "a (translatable) string and a space and another (translatable) string" etc.
For example :

S_IN.SPACE.S_MAINTENANCE => "In maintenance" in english, "En maintenance" in french => ok
S_IN.SPACE.S_GROUP => "In group" in english, "Dans le groupe" in french => impossible to translate
S_IN.SPACE.S_GROUPS => "In groups" in english, "Dans les groupes" in french => impossible to translate
S_HOSTS.SPACE.S_IN => "Hosts in" in english, "Contient les hôtes" in french => impossible to translate

The web frontend translation should be based on groupes of words and not single words. For example, replacing "S_IN.SPACE.S_MAINTENANCE" with a new "S_IN_MAINTENANCE" or "S_HOSTS.SPACE.S_IN" with "S_HOSTS_IN".

Issue Links

Activity

Hide
Oleksiy Zagorskyi added a comment -

Sébastien, welcome to the translation team !
Here is many similar issues with suggestions like your and I believe that they all will be fixed according to the ZBXNEXT-790 for Zabbix 2.0.[1-9]
Additionally I would like to let you know about issues ZBX-3271 and ZBX-4402 and see to a page http://www.zabbix.org/wiki/Translating_Zabbix

Regards,
Oleksiy

Show
Oleksiy Zagorskyi added a comment - Sébastien, welcome to the translation team ! Here is many similar issues with suggestions like your and I believe that they all will be fixed according to the ZBXNEXT-790 for Zabbix 2.0.[1-9] Additionally I would like to let you know about issues ZBX-3271 and ZBX-4402 and see to a page http://www.zabbix.org/wiki/Translating_Zabbix Regards, Oleksiy
Hide
richlv added a comment -

i'm not quite sure it's a good idea to fix it this way in 1.8 branch... this introduces lots of new translation strings - even if more correct, this will mean additional work to translators who might already have translated those partial strings (and who would not want to translate a bunch of new ones for 1.8 as they work on trunk already).

zalex, your opinion ?

Show
richlv added a comment - i'm not quite sure it's a good idea to fix it this way in 1.8 branch... this introduces lots of new translation strings - even if more correct, this will mean additional work to translators who might already have translated those partial strings (and who would not want to translate a bunch of new ones for 1.8 as they work on trunk already). zalex, your opinion ?
Hide
Oleksiy Zagorskyi added a comment -

Of course, I'm agree with Richlv for 1000%

Three hours ago (when Sanja assigned the issue himself) I checked the source of dev branch copied from and it was .... 1.8. I wanted to ask - WHY?
Why to spend time for 1.8 branch?
But I decides to be silent -> maybe it's a case to training/solve a not hard task or so.

I'm agree that would be better to resolve this issue for the 2.0 only.

Show
Oleksiy Zagorskyi added a comment - Of course, I'm agree with Richlv for 1000% Three hours ago (when Sanja assigned the issue himself) I checked the source of dev branch copied from and it was .... 1.8. I wanted to ask - WHY? Why to spend time for 1.8 branch? But I decides to be silent -> maybe it's a case to training/solve a not hard task or so. I'm agree that would be better to resolve this issue for the 2.0 only.
Hide
Alexander Sorokin added a comment -

It introduces 57 new strings. May be few more will be added.

Show
Alexander Sorokin added a comment - It introduces 57 new strings. May be few more will be added.
Hide
Alexander Sorokin added a comment -

Fixed for 1.8 in development branch svn://svn.zabbix.com/branches/dev/ZBX-4523

Show
Alexander Sorokin added a comment - Fixed for 1.8 in development branch svn://svn.zabbix.com/branches/dev/ZBX-4523
Hide
Alexander Sorokin added a comment -

Fixed for trunk in development branch svn://svn.zabbix.com/branches/dev/ZBX-4523-trunk

Show
Alexander Sorokin added a comment - Fixed for trunk in development branch svn://svn.zabbix.com/branches/dev/ZBX-4523-trunk
Hide
richlv added a comment - - edited

(1) that's at least 57 untranslated strings, introduced very lately in the branch lifecycle. based on zalex's opinion, i'd suggest not to do this for 1.8

<Sasha> Let's not do it in version 1.8. Too many untranslated new phrases. CLOSED

Show
richlv added a comment - - edited (1) that's at least 57 untranslated strings, introduced very lately in the branch lifecycle. based on zalex's opinion, i'd suggest not to do this for 1.8 <Sasha> Let's not do it in version 1.8. Too many untranslated new phrases. CLOSED
Hide
richlv added a comment - - edited

(2) trunk branch seems to add new S_ strings

I'm personally not sure worth to merge it to trunk as it is at the moment. Maybe would be better to discard these changes and to work only according to the ZBXNEXT-790 ?

<sanja> RESOLVED

Show
richlv added a comment - - edited (2) trunk branch seems to add new S_ strings I'm personally not sure worth to merge it to trunk as it is at the moment. Maybe would be better to discard these changes and to work only according to the ZBXNEXT-790 ? <sanja> RESOLVED
Hide
Alexey Fukalov added a comment - - edited

(3) [GUI]
Please review my changes in rev. 24783.

I reviewed 1.8 branch, don't forget to remove it CLOSED

Show
Alexey Fukalov added a comment - - edited (3) [GUI] Please review my changes in rev. 24783. I reviewed 1.8 branch, don't forget to remove it CLOSED
Hide
Alexey Fukalov added a comment - - edited

(4) [GUI]
Please review my changes in rev. 24819.

<sanja> CLOSED

Show
Alexey Fukalov added a comment - - edited (4) [GUI] Please review my changes in rev. 24819. <sanja> CLOSED
Hide
Alexander Sorokin added a comment -

Fixed in trunk, r24888

Show
Alexander Sorokin added a comment - Fixed in trunk, r24888

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: