[Zabbix-translators] single translation Project for all zabbix version ?

[Oleksiy Z. <ole...@za...>]

Hi all !

An idea came to me when I understood that different people translate 
different versions, which is not very good and not very easy to manage.
Problem is that it's hard to notice changes, hard to avoid duplicated 
work etc.

What do you think about for example merging all zabbix *versions* to 
single po file, have single Project available for translation with all 
strings from all versions?
Of identical stings will not be duplicated. Every unique string will be 
listed only once.

Then the Project may be used to prepare separate po version files before 
exporting to SVN branches. I know to do that.
Existing version projects will stay on the place and they will continue 
to reflect translation progress for each version, with READ-only access 
for translators.
Versioned projects could be automatically updated from the Project once 
every day automatically.

Drawbacks:
- some strings which were translated differently in different zabbix 
versions will be identical. It could be not very good for example for 
date/time formats.
- number of untranslated strings for new translators may be scary :), 
I'd expect +50-70% size from current 3.0
- when you translate/fix a string - you don't know zabbix version(s) it 
came from, although it could be improved by adding additional gettext 
comment which could indicate involved version(s) and will be visible in 
Pootle.

Advantages:
- easier for translators;
- 100% guaranty of avoiding duplicated work for translation and 
translation fixes;
- will resolve cases when Trunk branch stays not updated when people 
work on current major stable version - like it is currently for 3.0 and 
trunk.

It will require some scripting and automation work, but I think I'd be 
able to do that.

What do you think ?


--
Oleksiy