Mailinglist Archive: opensuse-translation (237 mails)

< Previous Next >
Re: [opensuse-translation] openSUSE Weblate
Den 11. okt. 2015 10:02, Ferdinand Galko skreiv:
I have made a closer look at openSUSE Weblate after the Tomáš Chvátal

Simple comparison:

I use Lokalize and subversion's commands update, status and commit in
99.9% of translation work.
I must have subversion installed, base knowledge about subversion background.
There must be local working directory in PC.
Statistics is available only once a day.

You are aware that Lokalize has built in project manager, right? With this, you have *continously* updated statistics; i.e., every time save your translation file, the statistics in the project view is updated (both with numbers and with colour-coded bars).

Download/upload .po files is simple in Weblate. There is not needed
any additional SW and any working directory to synchronise.

Is it easy to download and upload *all* the files in one go, and using the command line? That’s a requirement for me for having an efficient work flow.

The reason I’m asking, is that I’ve used other Web-based translation systems where the people implementing it said not to worry, as one could still download and upload files and translate offline, but where doing so involved clicking on each translation file (several clicks per file), wait a seemingly random amount of time (varying from a few minutes to a few hours) to receive an e-mail.

Also, there needs to be a way of mass-downloading the *template* files (.pot) instead of the translation files. Is this possible with Weblate? For my team, I need to do the merging with templates myself (for reasons I’ll not going into here, but they are good reasons, which saves work and improves quality).

Also, how are branches (i.e. 13.2, 42.0, Tumbleweed, trunk/Factory) in Weblate? Is there a separate repository/project/folder for each branch?

If all this is possible, I won’t see much of a problem with openSUSE using Weblate. I’ll be able to use my normal workflow (just replacing ‘svn up’ and ‘svn commit’ with two other commands). And for versioning, I’ll (hopefully) be able to continue to use the current SVN repository (perhaps with a different, more sensible, directory structure). As long as one person on each team was responsible for downloading from Weblate to SVN, and uploading from SVN to Weblate (two simple commands to run), other people could continue to use SVN (and other tools based on this, such as Vertaal) just like they do now.

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