Mailinglist Archive: opensuse-translation (94 mails)

< Previous Next >
Re: [opensuse-translation] Weblate / posummit status and possibilities
  • From: Andrea Turrini <andrea.turrini@xxxxxxxxx>
  • Date: Mon, 8 Apr 2013 14:42:24 +0200
  • Message-id: <CAFaemE9_1ebk0fTFAiQbV8oqTNuuN6X+wzz7QZmm8=26vLgpJA@mail.gmail.com>
2013/4/8 Tomáš Chvátal <tchvatal@xxxxxxx>:
Dne So 6. dubna 2013 18:14:39, Carlos E. R. napsal(a):
Indeed. I will not work via a web tool, no matter how good it is.


Why is that, if the tool is more convinient to use and easier to manage?

Because for instance I prefer to translate offline and then go online
just for updating/committing.
This is particularly important if you have a time/traffic bounded web
connection, or you translate on spare time when you do not have
internet connection.


We can still allow the write access in the end but you would loose all the
goodies.

I hope so.

Yes there were some paid translations, but that is not regular basis afaik, so
we can merge and review the "pro" stuff to be merged into openSUSE and vice
versa.

Provided that the po files for SLE and openSUSE are the same. Can you
ensure this? If not, what is the practical difference between keeping
different copies on a web site and keeping them on an svn server?
Moreover, I have seen in the faqs that it is possible to propagate
automatically changes from one branch to others. How do you manage
branches where by choice translations are different (for instance,
because the translation team has agreed for the next release on a
different translation style or on different translation rules)?

Ahem AFAIK the translations are merged anyway and whatever you contribute to
the openSUSE release is marked GPL/CC and others and will one day be included
in next SLE or actually used by anyone else interested.

From my point of view this is different: I am translating for openSUSE
following the translation rules Italian openSUSE translation team has
agreed on.
I care only about the result in openSUSE; I do not care whether these
translations are then used by others (they can, it is GPL/CC); it is
their problem to merge/adapt/rewrite my translations to their needs.
For sure I do not want that my work, done following agreed rules, is
wasted by commits done by translators from different teams following
different translation rules, just because a web tool is considered
more convenient to use and easier to manage.
BTW, the same happens now with the SVN server: I really dislike when
messages from other translations are merged and not marked as fuzzy,
but hopefully this is not happening any more.

Best,
Andrea
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-translation+owner@xxxxxxxxxxxx

< Previous Next >
List Navigation