[ZBX-4523] Impossible to correctly translate some parts of Zabbix Created: 2012 Jan 06  Updated: 2017 May 30  Resolved: 2012 Jan 18

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 1.8.10
Fix Version/s: 1.9.9 (beta)

Type: Incident report Priority: Major
Reporter: Sébastien Maccagnoni Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: internationalization, localization, translation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates ZBXNEXT-790 Clean up Zabbix front-end to make use... Closed

 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".

 Comments   
Comment by Oleksii Zagorskyi [ 2012 Jan 09 ]

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

Comment by richlv [ 2012 Jan 11 ]

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 ?

Comment by Oleksii Zagorskyi [ 2012 Jan 11 ]

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.

Comment by Alexander Sorokin (Inactive) [ 2012 Jan 11 ]

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

Comment by Alexander Sorokin (Inactive) [ 2012 Jan 11 ]

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

Comment by Alexander Sorokin (Inactive) [ 2012 Jan 11 ]

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

Comment by richlv [ 2012 Jan 11 ]

(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

Comment by richlv [ 2012 Jan 11 ]

(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

Comment by Alexey Fukalov [ 2012 Jan 16 ]

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

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

Comment by Alexey Fukalov [ 2012 Jan 17 ]

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

<sanja> CLOSED

Comment by Alexander Sorokin (Inactive) [ 2012 Jan 19 ]

Fixed in trunk, r24888

Generated at Thu Apr 25 12:00:57 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.