Mailinglist Archive: opensuse-translation (237 mails)

< Previous Next >
Re: [opensuse-translation] openSUSE Weblate
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2015-10-11 19:02, Karl Ove Hufthammer wrote:
Den 11. okt. 2015 18:42, Carlos E. R. skreiv:


What I was thinking of when writing the above was to *continue* to
use the current SVN server for hosting the translation files, but
uploading the results to Weblate (to automatically export them to
the various tools hosted in Git, so that they would be available in
openSUSE packages). It would work like this:

Ah, I see. Yes.


One person would run a simple script, called fetch-and-merge.sh,
for example, which would download the updated templates from
Weblate and (optionally, with a per-language setting) merge
existing translations with the templates. This script should be run
regularly (e.g., once per day).

A cronjob, running on the svn machine.


The translation templates and translation would be organized in
the ‘by-language’ directory structure detailed in
http://pology.nedohodnik.net/doc/user/en_US/ch-summit.html#sec-susetup


so that each team had a separate directory to do all their work in
(which is the preferred directory layout for most translation tools
too).

Is it not how is it in the current svn tree? :-?


The various translators would use the tools they prefer to update
the translation files. Some teams may use Vertaal to coordinate
everything.

One person would run a simple script, called
upload-translations.sh, for example, to mass-upload all the
translations to Weblate.

And other teams would be able to use weblate if they prefer.

What about the stripped comments? Maybe they would remain in the SV,
which would be the master copy. Per team choice.


Variant (perhaps the preferred one?): Each *team coordinator* would
be responsible for running upload-translations.sh and/or
fetch-and-merge.sh for his/her language.

If Weblate supported command-line based mass-downloading of
templates files (*.pot) and mass-uploading of translations files
(*.po), this would actually be *very* easy to accomplish. We would
only need a few line of shell scripting.

This would be a nice solution for all, yes :-)

- --
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 "Bottle" (Minas Tirith))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iF4EAREIAAYFAlYam2cACgkQja8UbcUWM1zc0AD/feuGEaH5r8CkGXn9Pn8Gv+QZ
A1XNmW4aOWREOr+5bEgA/R2XLZxCdnNe7ooBiUmiV1lce52oCr2QoWCOaF2zUdrz
=64iy
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-translation+owner@xxxxxxxxxxxx

< Previous Next >
This Thread