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

[Adail H. <the...@gm...>]

Is not betther a script to send the translation of identical strings from
current to old versions ?

For example... I translate zbx 3.0... 100%... the "script" get the strings
from zbx3.0 and send back to 2.4.

If I have time... I back on 2.4 and translate the missing strings...

Theoretically... "dont have a new string" on "old versions of zabbix"... (I
think is the tendence).



Adail Horst
OCA/OCP - Oracle Application Server
ZABBIX Certified Specialist
http://www.spinola.net.br/blog (Blog sobre Zabbix e tecnologia)
http://zabbixone.com livro "De A a Zabbix"

On Tue, Feb 23, 2016 at 9:06 AM, Oleksiy Zagorskyi <
ole...@za...> wrote:

> 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
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Zabbix-translators mailing list
> Zab...@li...
> https://lists.sourceforge.net/lists/listinfo/zabbix-translators
>