Mailinglist Archive: opensuse-translation (237 mails)

< Previous Next >
[opensuse-translation] Conflict with SLES translations [Was: openSUSE Weblate]
Hash: SHA256

On 2015-10-19 18:46, Richard Brown wrote:

On 19 October 2015 at 18:18, Carlos E. R. <carlos.e.r@xxxxxxxxxxxx>
In fact, if my translations are going to end up in SLES, we have
a problem. And not only me, other translators have said so, in
this mail list; some very recently.

Carlos, you realise your translations are contributed to an OPEN
Project correct?

Of course I do. Or we do, because it is not only me; as usual, I'm
only once which talks more ;-)

There is in fact an ethics conflict, like it or not. Me, for instance,
object to translate a file that an SLES paid translator intended or
hoped to translate, because I'm reducing his earnings, his sustenance.

Some one from another team said here, not a week ago, that he had team
member(s) whose employer would be quite annoyed at finding that he was
translating for free files for SLES, that his company intended to
translate. A very serious concern, he said.

Translators in my team told me in the past that they did not want to
translate applications that were only available on SLES - the typical
example was the yast registration module.

Others simply object to translate something that ends in SLES, and not
being paid for it.

But nobody can object if an SLES paid translator picks the translation
from an openSUSE, and uses it as is. The gettext system does not track
credits, and the translations are open.

By the way... I just looked at a random 2013 po from yast (what I have
available this instant without moving from my comfortable chair). It
is copyrighted by SUSE (some by SuSE), there is no mention of GPL inside.

- --
Cheers / Saludos,

Carlos E. R.

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

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

< Previous Next >
This Thread