[wesnoth-i18n] syncing translations between branches

Nils Kneuper crazy-ivanovic at gmx.net
Sun Feb 27 11:56:05 UTC 2022


Hi Michal,

The most used approach by many teams is to not start work on development branch
until it is "close to complete" and nearing a stable release. Until then, they
work on and improve "stable" and the files get committed to both branches. Yes,
this means plenty untranslated / fuzzy strings in development, but at least you
are not working against a moving target.

In the past we also had a script called po2po but there were some problems with
it, especially when it came to things like plural forms and handling them
correctly. Not sure if it gracefully handled the same string existing twice in
the files and what version it did prefer in that case. If I recall correctly,
that script just appended the 2nd textdomain to the first file and then ran a
pot-update against it to get rid of the stuff not existing in the textdomain.

Hope that helps with the background information.

Have a great day,
Nils Kneuper aka Ivanovic


Am 27.02.22 um 11:29 schrieb Michal Žejdl:
> Hi,
>
> tired using vimdiff while trying to transfer already completed translations from
> 1.16 to master after its last POT update I finally gave up and wrote a script:
>
> https://github.com/celerini/scripts/blob/master/msync.sh
>
>
> I ran it on all .po files in wesnoth repo. It took about 5 minutes and resulted
> in nearly 3000 translation being transferred from 1.16 to master:
>
> https://github.com/celerini/wesnoth/tree/transync/po
>
>
> I would like get any feedback because I wonder if
>
> - I am doing something stupid what other maintainers solved in some better way
>
> - somebody find it useful, or find an error in her language (it works for me)
>
> - it can be ideally used in upstream after POT update to merge messages that got
> splitted by development (branches, delayed POT updates)
>
>
> I am running the script on Fedora (Linux). For those which already have some
> work in progress not submitted to upstream yet and can not run it on their
> system I offer to sync it for you, when you send me your work and point to
> source of already translated messages (probably 1.16 now).
>
>
> sincerely, your Czech maintainer
>




More information about the i18n mailing list