Mailinglist Archive: opensuse-translation (237 mails)

< Previous Next >
Re: [opensuse-translation] openSUSE Weblate
Den 14. okt. 2015 18:21, Luiz Fernando Ranghetti skreiv:
>I was told on IRC that weblate does support branches, but currently there are
>none, because SLE12sp1/Leap and Tumbleweed are pretty much all in sync
>currently.
>
>Wonder if weblate will merge the different branches automatically, if the
>translator translates strings in one branch, which are valid for all the
>branches.


Maybe something like the summit operation of pology [1] which some KDE
teams use (it creates a po file from multiple branches)

Actually I (the Norwegian Nynorsk team) already *use* the Pology summit framework for translating openSUSE. It’s working very well. Currently, I use it to simultaneously translate openSUSE 13.2 and trunk. (I had planned to also add SLES 12 SP1 to the mix, for use in Tumbleweed, but I never got confirmation on whether it was OK for non-paid translator to commit files to the SLES 12 SP1 branch in SVN.)

If it’s easy fast and easy to download and upload the translation files from/to Weblate and branches are supported there, I’ll continue using this approach (and of course I’ll offer any scripts and config files to other teams that want to use it).

BTW, the Pology summit framework is much more powerful than a simple ‘handle the same file in two branches’ approach. For example, it can handle applications that are split into several catalogues in some branches (e.g. an application in ‘stable’ is split into a application + library in ‘trunk’ (or the other way around, where several files are merged into one, but only in certain branches)).

It also has intelligent ordering of strings: If two strings (from different branches) are very similar, they are placed next to each other in the resulting file. The translator can then easily compare them. So if a string in ‘stable’ is improved in ‘trunk’, e.g. to make it clearer (but the stable English string is not changed, perhaps because of a string freeze), the translator can choose to apply the translation of the improved string to *both* ‘stable’ and ‘trunk’, to the benefit of the users of the translated application.

And Pology has integration with Lokalize, where you can choose to show only strings from a certain branch (e.g. to prioritise translation of strings in the branch which is due to release soon). (Personally, I have never had any use of this branch-filtering feature, but I have found Pology filtering with Lokalize synchronisation/filtering *in general* to be quite useful.)

--
Karl Ove Hufthammer
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-translation+owner@xxxxxxxxxxxx

< Previous Next >
This Thread
Follow Ups