[Translators] VLC on Transifex

[Christoph Miebach]

Hello!

I am trying to clarify this. Feel free to ask again at any topics I fail...

The projects on transifex are not replacing the git version on videolan. 
They are not even automatically pushed upstream. The old way is still 
completely valid and in fact most of the steps will have to be done when 
using transifex.

However, using transifex might be less work for someone, that's why we 
offer it. You will get the current versions of the files and don't have 
to worry about translating deprecated strings. Maybe you even find 
co-translators that way. But you will not have to use it. I don't even 
know if you like the webinterface better than what you use right now 
(plain text editor or poedit maybe).

Use case might be:
-Get the current translation state (from git or from transifex)
-translate locally (as before)
-some (original) strings get updated on transifex
-push your local version to transifex and re-download the merged new 
file back to your local disc (contains your translation and all modified 
strings)

For a release you can send your file as before or maybe the one 
available from transifex can be used directly. If the headers are broken 
(basically removing translator's names) by transifex some guy at 
videolan would have to repair these headers. So the old way might be 
less work for videolan.

On 01.05.2012 13:44, Gaëtan Rousseaux wrote:
>   * First there's a problem with Transifex. It seems that there are two
>     project for VLC translation, yours and another one:

There are even more ;-) I set up a new sandbox.

>     *https://www.transifex.net/projects/p/vlc/*

I can't say anything to this one, for I am not related.

>     *https://www.transifex.net/projects/p/vlc-trans/* (with these
>     languages: English, Turkish,
[...]
Adding new (more or less common) languages is very easy. For languages 
that don't exist in transifex it would be a little more difficult.
This one is in use right now, the existing language teams all include 
the current maintainer.

>     For both projects, there are three more languages requested, but not
>     the same for the two projects, so in fact 6 new languages. That's
>     more than 30 languages until now seperated in two project with
>     different maintainers. That could generate some troubles.

The new requests are from transifex translators who found the project 
and like to help. I did not accept this request blindly, for many 
languages already have a maintainer (not all use transifex). I point 
them to the current maintainer to avoid having vlc translated twice 
(avoid double work).

>   * What happened when an uodate of VLC contains more strings. Do you
>     merge the former po files in the new one, or should I ask it to
>     Chrisotphe Mutricy. What I did until now?

Setting up a new transifex (sub-) project with the current git state is 
very easy and can be done automatically (except the languages not yet 
available at transifex). Check the sandox:

https://www.transifex.net/projects/p/videolan/

If the pot file changes, vlc-trans has the newest version within a day 
(checks for updates daily). Merging your old translations is done of 
course (we do not want to throw away good work). If you upload a newer 
version transifex does the merging for you.

The normal old workflow on merging will not be changed.

I hope that helps.

Christoph