Leap/SLE translations pushed to Tumbleweed?

classic Classic list List threaded Threaded
32 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Leap/SLE translations pushed to Tumbleweed?

Alexander Melentev
Hi all
I've just noticed it today, but hope somebody will give a hint when
this has actually happened. I ran zypper and found out that it's
translations are not taken from our svn trunk anymore.
Since SLE is the only alternative source of translations I know, I
assume keichwa or somebody else (un)intentionally changed the source
of translations for zypper and maybe other software too (however, YaST
still looks fine). So once again we face the problem of severe
differences between SLE and community translations, still without a
decent solution.
I know that it matters only for a subset of "officially supported"
languages, but still I'd like to hear any ideas from you. What do you
think about it?
--
Regards, Minton.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Antoine Belvire
Hello,

Le 05/03/2016 14:05, Alexander Melentev a écrit :
> Hi all
> I've just noticed it today, but hope somebody will give a hint when
> this has actually happened. I ran zypper and found out that it's
> translations are not taken from our svn trunk anymore.

I did a bug report for this:
https://bugzilla.opensuse.org/show_bug.cgi?id=968588.

It was triggered by this: https://build.opensuse.org/request/show/360451 
which was decided because of this bug:
https://bugzilla.novell.com/show_bug.cgi?id=948924.

Regards,

Antoine
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Stephan Kulow-3
Am 05.03.2016 um 16:30 schrieb Antoine Belvire:

> Hello,
>
> Le 05/03/2016 14:05, Alexander Melentev a écrit :
>> Hi all
>> I've just noticed it today, but hope somebody will give a hint when
>> this has actually happened. I ran zypper and found out that it's
>> translations are not taken from our svn trunk anymore.
>
> I did a bug report for this:
> https://bugzilla.opensuse.org/show_bug.cgi?id=968588.
>
> It was triggered by this: https://build.opensuse.org/request/show/360451
> which was decided because of this bug:
> https://bugzilla.novell.com/show_bug.cgi?id=948924.

Are you missing translations or are there bugs in the SLE translations?

Greetings, Stephan

--
Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die
ganze Welt an Arsch offen hat, oder grad deswegn.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Antoine Belvire
Le 07/03/2016 07:55, Stephan Kulow a écrit :

> Am 05.03.2016 um 16:30 schrieb Antoine Belvire:
>> Hello,
>>
>> Le 05/03/2016 14:05, Alexander Melentev a écrit :
>>> Hi all
>>> I've just noticed it today, but hope somebody will give a hint when
>>> this has actually happened. I ran zypper and found out that it's
>>> translations are not taken from our svn trunk anymore.
>>
>> I did a bug report for this:
>> https://bugzilla.opensuse.org/show_bug.cgi?id=968588.
>>
>> It was triggered by this: https://build.opensuse.org/request/show/360451
>> which was decided because of this bug:
>> https://bugzilla.novell.com/show_bug.cgi?id=948924.
>
> Are you missing translations or are there bugs in the SLE translations?
>
> Greetings, Stephan

I can speak only for French: missing translations and strange
translations. Community version is clearly better to me.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Stephan Kulow-3
On 07.03.2016 08:07, Antoine Belvire wrote:

> Le 07/03/2016 07:55, Stephan Kulow a écrit :
>> Am 05.03.2016 um 16:30 schrieb Antoine Belvire:
>>> Hello,
>>>
>>> Le 05/03/2016 14:05, Alexander Melentev a écrit :
>>>> Hi all
>>>> I've just noticed it today, but hope somebody will give a hint when
>>>> this has actually happened. I ran zypper and found out that it's
>>>> translations are not taken from our svn trunk anymore.
>>>
>>> I did a bug report for this:
>>> https://bugzilla.opensuse.org/show_bug.cgi?id=968588.
>>>
>>> It was triggered by this: https://build.opensuse.org/request/show/360451
>>> which was decided because of this bug:
>>> https://bugzilla.novell.com/show_bug.cgi?id=948924.
>>
>> Are you missing translations or are there bugs in the SLE translations?
>>
>> Greetings, Stephan
>
> I can speak only for French: missing translations and strange
> translations. Community version is clearly better to me.

Hi Antoine,

Please report strange translations as openSUSE Leap bugs - no one gains
anything if you leave strange translations to Leap users.

Translations that exist in master, but are not in TW zypper are a bug,
but we can't continue with "them vs us" when it comes to supported
languages.

If the SLE translators doesn't listen to your feedback, we need to talk
to them again - but first we need that feedback. I can't talk to them,
this needs to be a discussion held in french ;)

Greetings, Stephan

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Alexander Melentev
Hi Stephan,

I can confirm Antoine's problem descriptions for Russian also, a lot
of SLE translations were made using machine translation some years ago
and also merged to openSUSE. I've joined openSUSE-i18n a few days
before 11.0 release and all these years were spent in wiping
out/fixing/polishing those strange translations. Currently I have
thousands of differences and I can hardly imagine reporting them all.
It looks like other languages have similar problems: we can't push our
translations to SLE, cause there is another team with their own
translations, but we cannot accept SLE translations to openSUSE, cause
of lower quality. Currently it looks like SLE is considered as a
better source of translations while it is not (well, at least for
French and Russian, but probably for some other languages also). Maybe
it makes sense to prefer openSUSE-i18n over SLE or build separate lang
packages with community translations for Leap, so that users can
select what is better for them? Cause even if we all somehow agree on
fixing all the translations, it is a huge work which will take a lot
of time.

2016-03-07 12:47 GMT+03:00 Stephan Kulow <[hidden email]>:

> On 07.03.2016 08:07, Antoine Belvire wrote:
>> Le 07/03/2016 07:55, Stephan Kulow a écrit :
>>> Am 05.03.2016 um 16:30 schrieb Antoine Belvire:
>>>> Hello,
>>>>
>>>> Le 05/03/2016 14:05, Alexander Melentev a écrit :
>>>>> Hi all
>>>>> I've just noticed it today, but hope somebody will give a hint when
>>>>> this has actually happened. I ran zypper and found out that it's
>>>>> translations are not taken from our svn trunk anymore.
>>>>
>>>> I did a bug report for this:
>>>> https://bugzilla.opensuse.org/show_bug.cgi?id=968588.
>>>>
>>>> It was triggered by this: https://build.opensuse.org/request/show/360451
>>>> which was decided because of this bug:
>>>> https://bugzilla.novell.com/show_bug.cgi?id=948924.
>>>
>>> Are you missing translations or are there bugs in the SLE translations?
>>>
>>> Greetings, Stephan
>>
>> I can speak only for French: missing translations and strange
>> translations. Community version is clearly better to me.
>
> Hi Antoine,
>
> Please report strange translations as openSUSE Leap bugs - no one gains
> anything if you leave strange translations to Leap users.
>
> Translations that exist in master, but are not in TW zypper are a bug,
> but we can't continue with "them vs us" when it comes to supported
> languages.
>
> If the SLE translators doesn't listen to your feedback, we need to talk
> to them again - but first we need that feedback. I can't talk to them,
> this needs to be a discussion held in french ;)
>
> Greetings, Stephan
>
> --
> To unsubscribe, e-mail: [hidden email]
> To contact the owner, e-mail: [hidden email]
>



--
Regards, Minton.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Luiz Fernando Ranghetti-2
Hi,

The best would be: for everything the community translate, always use
community translations for openSUSE products. As simple as that.

Regards,

Luiz
pt_BR translator

2016-03-07 10:04 GMT-03:00 Alexander Melentev <[hidden email]>:

> Hi Stephan,
>
> I can confirm Antoine's problem descriptions for Russian also, a lot
> of SLE translations were made using machine translation some years ago
> and also merged to openSUSE. I've joined openSUSE-i18n a few days
> before 11.0 release and all these years were spent in wiping
> out/fixing/polishing those strange translations. Currently I have
> thousands of differences and I can hardly imagine reporting them all.
> It looks like other languages have similar problems: we can't push our
> translations to SLE, cause there is another team with their own
> translations, but we cannot accept SLE translations to openSUSE, cause
> of lower quality. Currently it looks like SLE is considered as a
> better source of translations while it is not (well, at least for
> French and Russian, but probably for some other languages also). Maybe
> it makes sense to prefer openSUSE-i18n over SLE or build separate lang
> packages with community translations for Leap, so that users can
> select what is better for them? Cause even if we all somehow agree on
> fixing all the translations, it is a huge work which will take a lot
> of time.
>
> 2016-03-07 12:47 GMT+03:00 Stephan Kulow <[hidden email]>:
>> On 07.03.2016 08:07, Antoine Belvire wrote:
>>> Le 07/03/2016 07:55, Stephan Kulow a écrit :
>>>> Am 05.03.2016 um 16:30 schrieb Antoine Belvire:
>>>>> Hello,
>>>>>
>>>>> Le 05/03/2016 14:05, Alexander Melentev a écrit :
>>>>>> Hi all
>>>>>> I've just noticed it today, but hope somebody will give a hint when
>>>>>> this has actually happened. I ran zypper and found out that it's
>>>>>> translations are not taken from our svn trunk anymore.
>>>>>
>>>>> I did a bug report for this:
>>>>> https://bugzilla.opensuse.org/show_bug.cgi?id=968588.
>>>>>
>>>>> It was triggered by this: https://build.opensuse.org/request/show/360451
>>>>> which was decided because of this bug:
>>>>> https://bugzilla.novell.com/show_bug.cgi?id=948924.
>>>>
>>>> Are you missing translations or are there bugs in the SLE translations?
>>>>
>>>> Greetings, Stephan
>>>
>>> I can speak only for French: missing translations and strange
>>> translations. Community version is clearly better to me.
>>
>> Hi Antoine,
>>
>> Please report strange translations as openSUSE Leap bugs - no one gains
>> anything if you leave strange translations to Leap users.
>>
>> Translations that exist in master, but are not in TW zypper are a bug,
>> but we can't continue with "them vs us" when it comes to supported
>> languages.
>>
>> If the SLE translators doesn't listen to your feedback, we need to talk
>> to them again - but first we need that feedback. I can't talk to them,
>> this needs to be a discussion held in french ;)
>>
>> Greetings, Stephan
>>
>> --
>> To unsubscribe, e-mail: [hidden email]
>> To contact the owner, e-mail: [hidden email]
>>
>
>
>
> --
> Regards, Minton.
> --
> To unsubscribe, e-mail: [hidden email]
> To contact the owner, e-mail: [hidden email]
>
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Stephan Kulow-3
On 07.03.2016 15:00, Luiz Fernando Ranghetti wrote:
> Hi,
>
> The best would be: for everything the community translate, always use
> community translations for openSUSE products. As simple as that.
>
I can understand your point of view, but it's not "as simple as that".

Greetings, Stephan

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Stephan Kulow-3
In reply to this post by Alexander Melentev
On 07.03.2016 14:04, Alexander Melentev wrote:

> Hi Stephan,
>
> I can confirm Antoine's problem descriptions for Russian also, a lot
> of SLE translations were made using machine translation some years ago
> and also merged to openSUSE. I've joined openSUSE-i18n a few days
> before 11.0 release and all these years were spent in wiping
> out/fixing/polishing those strange translations. Currently I have
> thousands of differences and I can hardly imagine reporting them all.
> It looks like other languages have similar problems: we can't push our
> translations to SLE, cause there is another team with their own
> translations, but we cannot accept SLE translations to openSUSE, cause
> of lower quality. Currently it looks like SLE is considered as a
> better source of translations while it is not (well, at least for
> French and Russian, but probably for some other languages also). Maybe
> it makes sense to prefer openSUSE-i18n over SLE or build separate lang
> packages with community translations for Leap, so that users can
> select what is better for them? Cause even if we all somehow agree on
> fixing all the translations, it is a huge work which will take a lot
> of time.

Hi Alexander,

That sounds severe indeed. The main reason we can't just throw away the
SLE translations is that the SLE translators also translate the manuals
and having the tools and the documentation in sync is very valuable to
customers. Now if the documentation also uses this machine translation
way you describe, it makes you wonder how useful the Russian manual is ;(

But as I said previously: if the problem with our translations is so
bad, we need to fix it for real. Not just hide it for Tumbleweed. So
it's great we're having this discussion, because I'm certain in the end
we will see a solution that will please all Russian (open)SUSE users.

Greetings, Stephan

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Carlos E. R.-2
In reply to this post by Stephan Kulow-3
On 2016-03-07 15:42, Stephan Kulow wrote:
> On 07.03.2016 15:00, Luiz Fernando Ranghetti wrote:
>> Hi,
>>
>> The best would be: for everything the community translate, always use
>> community translations for openSUSE products. As simple as that.
>>
> I can understand your point of view, but it's not "as simple as that".

It has been that way since ever. I can tell that the Spanish team
rejected the SLE translation and we have always done our own
translation. There were always different and separate translation
directories for openSUSE and SLE. If you insist on on merging them, you
get these problems.

--
Cheers / Saludos,

                Carlos E. R.
                (from 13.1 x86_64 "Bottle" at Telcontar)


signature.asc (205 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Richard Brown
In reply to this post by Stephan Kulow-3
On 7 March 2016 at 15:42, Stephan Kulow <[hidden email]> wrote:
> On 07.03.2016 15:00, Luiz Fernando Ranghetti wrote:
>> Hi,
>>
>> The best would be: for everything the community translate, always use
>> community translations for openSUSE products. As simple as that.
>>
> I can understand your point of view, but it's not "as simple as that".
>

Agreed, I think a much better starting point is by filing bugs against
those translations in Leap and Tumbleweed that have been contributed
to openSUSE from SUSE

Remember, it's an equally valid point of view that SUSE is a community
contributor to openSUSE too..

who is to say that those translations are innately more invalid than
those from other community members?

Both points of view are valid, but nothing can be fixed in either
direction with concrete, solid, measurable items requiring actions

So, please, please, file the bugs
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Stephan Kulow-3
In reply to this post by Carlos E. R.-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 07.03.2016 um 15:48 schrieb Carlos E. R.:

> On 2016-03-07 15:42, Stephan Kulow wrote:
>> On 07.03.2016 15:00, Luiz Fernando Ranghetti wrote:
>>> Hi,
>>>
>>> The best would be: for everything the community translate,
>>> always use community translations for openSUSE products. As
>>> simple as that.
>>>
>> I can understand your point of view, but it's not "as simple as
>> that".
>
> It has been that way since ever. I can tell that the Spanish team
That is far from true. What is true is that we had a couple of
openSUSE releases over the last years which were completely decoupled
from SLE releases and we fixed that for Leap 42.1.

What is also true that we failed to involve the SLE translators in the
process.

Greetings, Stephan

- --
Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die
ganze Welt an Arsch offen hat, oder grad deswegn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlbdsQwACgkQwFSBhlBjoJY8pACeIah840hfWcAp6Dc9pmxlUNE0
yAYAniY11H+OvFMewjPGv4RkX+nEYzYd
=wNC+
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Luiz Fernando Ranghetti-2
In reply to this post by Richard Brown
2016-03-07 11:51 GMT-03:00 Richard Brown <[hidden email]>:

> On 7 March 2016 at 15:42, Stephan Kulow <[hidden email]> wrote:
>> On 07.03.2016 15:00, Luiz Fernando Ranghetti wrote:
>>> Hi,
>>>
>>> The best would be: for everything the community translate, always use
>>> community translations for openSUSE products. As simple as that.
>>>
>> I can understand your point of view, but it's not "as simple as that".
>>
>
> Agreed, I think a much better starting point is by filing bugs against
> those translations in Leap and Tumbleweed that have been contributed
> to openSUSE from SUSE
>
> Remember, it's an equally valid point of view that SUSE is a community
> contributor to openSUSE too..
>
> who is to say that those translations are innately more invalid than
> those from other community members?
>
> Both points of view are valid, but nothing can be fixed in either
> direction with concrete, solid, measurable items requiring actions
>
> So, please, please, file the bugs
> --

Hi,

What if, as an hypothetical example, there is an translation error/new
strings in zypper that only affect Leap, but not SLE. The SLE
translators will fix it or not as it's out of they job scope?

Just for the records the pt_BR don't have all this mess, its just
different, both are correct and valid, but I prefer our... :-P

Regards,

Luiz
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Richard Brown
On 7 March 2016 at 17:52, Luiz Fernando Ranghetti <[hidden email]> wrote:

> 2016-03-07 11:51 GMT-03:00 Richard Brown <[hidden email]>:
>> On 7 March 2016 at 15:42, Stephan Kulow <[hidden email]> wrote:
>>> On 07.03.2016 15:00, Luiz Fernando Ranghetti wrote:
>>>> Hi,
>>>>
>>>> The best would be: for everything the community translate, always use
>>>> community translations for openSUSE products. As simple as that.
>>>>
>>> I can understand your point of view, but it's not "as simple as that".
>>>
>>
>> Agreed, I think a much better starting point is by filing bugs against
>> those translations in Leap and Tumbleweed that have been contributed
>> to openSUSE from SUSE
>>
>> Remember, it's an equally valid point of view that SUSE is a community
>> contributor to openSUSE too..
>>
>> who is to say that those translations are innately more invalid than
>> those from other community members?
>>
>> Both points of view are valid, but nothing can be fixed in either
>> direction with concrete, solid, measurable items requiring actions
>>
>> So, please, please, file the bugs
>> --
>
> Hi,
>
> What if, as an hypothetical example, there is an translation error/new
> strings in zypper that only affect Leap, but not SLE. The SLE
> translators will fix it or not as it's out of they job scope?

SUSE are committed to ensuring that both SLE and Leap share as much
code and content that is practical, and that their contributions to
Leap via SLE are all of a high quality

So, firstly, a Leap-only bug from a SLE translation error should be
pretty much impossible

But if it did happen, I would expect the bug to be fixed

openSUSE 'going it's own way' should only be a last resort if all
involved haven't done our best to fix the other real issues that
triggered the problem.

>
> Just for the records the pt_BR don't have all this mess, its just
> different, both are correct and valid, but I prefer our... :-P
>
> Regards,
>
> Luiz
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Carlos E. R.-2
In reply to this post by Stephan Kulow-3
On 2016-03-07 17:49, Stephan Kulow wrote:

> Am 07.03.2016 um 15:48 schrieb Carlos E. R.:
>> On 2016-03-07 15:42, Stephan Kulow wrote:
>>> On 07.03.2016 15:00, Luiz Fernando Ranghetti wrote:
>>>> Hi,
>>>>
>>>> The best would be: for everything the community translate,
>>>> always use community translations for openSUSE products. As
>>>> simple as that.
>>>>
>>> I can understand your point of view, but it's not "as simple as
>>> that".
>
>> It has been that way since ever. I can tell that the Spanish team
> That is far from true. What is true is that we had a couple of
> openSUSE releases over the last years which were completely decoupled
> from SLE releases and we fixed that for Leap 42.1.
Not for Spanish. We took good care to reject the SLE translations and
use our own. We voted years ago and took a decision.

Leap was not translated at all on our part.

--
Cheers / Saludos,

                Carlos E. R.
                (from 13.1 x86_64 "Bottle" at Telcontar)


signature.asc (205 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Antoine Belvire
In reply to this post by Stephan Kulow-3
Hi Stephan, hi all,

Le 07/03/2016 10:47, Stephan Kulow a écrit :
> Hi Antoine,
>
> Please report strange translations as openSUSE Leap bugs - no one gains
> anything if you leave strange translations to Leap users.

Well, the strangest thing about this, is that for Leap 42.1, the French
translation of zypper comes from community!

antoine@linux-96b1:~> lsb_release -d
Description:    openSUSE Leap 42.1 (x86_64)

antoine@linux-96b1:~> msgunfmt
/usr/share/locale/fr/LC_MESSAGES/zypper.mo | grep Translator
"Last-Translator: Antoine Belvire <[hidden email]>\n"
antoine@linux-96b1:~>

Strange to me but I like this translation :)

> Translations that exist in master, but are not in TW zypper are a bug,
> but we can't continue with "them vs us" when it comes to supported
> languages.
> If the SLE translators doesn't listen to your feedback, we need to talk
> to them again - but first we need that feedback. I can't talk to them,
> this needs to be a discussion held in french ;)

Glad to hear that it can be considered as a bug for Tumbleweed.

Be assured that I don't like to say "them vs us", I don't intend to… The
thing is, I'd like to translate too, not just report bugs and give
feedbacks ;)

It would be cool if just everybody could translate openSUSE for any
language, SLE's translators as everybody else. I mean, inside a team,
with some rules of course. We have l10n.opensuse.org but there are just
a few projects open and no team functionality yet as far as I know.

I don't know SLE translators. Do you know what is the best way to
contact them? Is there a better way than this thread or this bug report?

Regards,

--
Antoine
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Alexander Melentev
In reply to this post by Stephan Kulow-3
2016-03-07 17:47 GMT+03:00 Stephan Kulow <[hidden email]>:
> That sounds severe indeed. The main reason we can't just throw away the
> SLE translations is that the SLE translators also translate the manuals
> and having the tools and the documentation in sync is very valuable to
> customers. Now if the documentation also uses this machine translation
> way you describe, it makes you wonder how useful the Russian manual is ;(
Well, even if I'm sure this manual is not that useful in Russian, that
is not my main concern. I wasn't suggesting to "just throw away"
anything, exactly because SLE translations are paid translations and
they are there to add value to SLE releases to make customers happier.
But I have nothing to do with this, I am community volunteer who
translates openSUSE releases only, cause community contributions to
SLE branches are forbidden. My point was about Leap (even though it is
SLE-based) and TW as they are still openSUSE releases which deserve
(and are implied) to have openSUSE translations.

> But as I said previously: if the problem with our translations is so
> bad, we need to fix it for real. Not just hide it for Tumbleweed. So
> it's great we're having this discussion, because I'm certain in the end
> we will see a solution that will please all Russian (open)SUSE users.
I hope so, too. I am really willing to rectify this situation somehow,
but reporting translation differences is a dead-born idea. yast+lcn
have almost 35k messages, some SLE translations are OK, just different
but some are horrible,but even if we all be really kind and say that
only 10% worth a report, doing so with 10 bugreports a day will take
me almost a year. So I would really like to have some other way to fix
those issues.


--
Regards, Minton.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Alexander Melentev
In reply to this post by Richard Brown
2016-03-07 17:51 GMT+03:00 Richard Brown <[hidden email]>:

> On 7 March 2016 at 15:42, Stephan Kulow <[hidden email]> wrote:
>> On 07.03.2016 15:00, Luiz Fernando Ranghetti wrote:
>>> Hi,
>>>
>>> The best would be: for everything the community translate, always use
>>> community translations for openSUSE products. As simple as that.
>>>
>> I can understand your point of view, but it's not "as simple as that".
>>
>
> Agreed, I think a much better starting point is by filing bugs against
> those translations in Leap and Tumbleweed that have been contributed
> to openSUSE from SUSE
Please see my simple calculation in previous mail proving it
impossible for one man.
Also I am pretty sure that e.g. Russian translation is not coming from
SUSE at all, so a separate company took care of it.

> Remember, it's an equally valid point of view that SUSE is a community
> contributor to openSUSE too..
Oh, please don't bring this fairy tale here, we all live in the real
world and understand that "All contributors are equal, but SUSE is
more equal than others". But we are all fine with that situation,
cause it was always like that. I am forbidden to fix any error in SLE
translations, but SUSE developers prefer SLE translations over
community ones even for community releases like openSUSE. It is more
or less understandable for Leap as it is "SLE-based", but pushing it
to Tumbleweed is just too much.

I am not a professional translator at all, but I've spent many years
translating openSUSE. People reported the issues they saw and I
fixed'em and reported back, but when Leap was released I had plently
of awkward moments with other guys from Russian community as I had to
reject thei reports and say things like "It wasn't me", "I have
nothing to do with this" and "Sorry, I can't fix this for you". I
completely understand that there was no bad will in pushing SLE
translations to Leap (for e.g. Russian the decision was just plain
wrong), but please understand that I have only good will either trying
to prevent pushing them at least to TW.
> who is to say that those translations are innately more invalid than
> those from other community members?
And who is to say those translations are better than community ones?
"Equality" works in both directions =) Well, the translations quality
is completely different issue. I can say for my native language only
and I understand that my word is not a proof here, but that's the only
feedback you have: my translations are not perfect, I know this, but
the quality of SLE translations is really different from file to file.
A couple of recent yast modules had pretty good translations and I
have even merged them to our trunk to not duplicate the work, but the
older the message is, the higher chances are its translation is
rubbish. As the merge of "rubbish" messages happened many years ago
let's call them "legacy translations". So the main problem with SLE
translations quality as I see it is that no proofreading was done for
legacy ones.
Current state of things is broken: we have two different sets of
translations and no way to collaborate on merging them without
conflict of interests (SLE translators are paid ones and we are
community volunteers). I am more than willing to help fix this, but we
really need some more valid way than reporting issues one-by-one...

> Both points of view are valid, but nothing can be fixed in either
> direction with concrete, solid, measurable items requiring actions
Would you mind to re-phrase? I've lost your point here.

> --
> To unsubscribe, e-mail: [hidden email]
> To contact the owner, e-mail: [hidden email]
>



--
Regards, Minton.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Stephan Kulow-3
In reply to this post by Alexander Melentev
Am 07.03.2016 um 23:53 schrieb Alexander Melentev:
> but some are horrible,but even if we all be really kind and say that
> only 10% worth a report, doing so with 10 bugreports a day will take
> me almost a year. So I would really like to have some other way to fix
> those issues.
>
One bug report stating 10 horrible examples will be enough for us to get
back to the SLE translators. Remember we pay them to do good
translations, so we expect better than horrible.

Greetings, Stephan

--
Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die
ganze Welt an Arsch offen hat, oder grad deswegn.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Leap/SLE translations pushed to Tumbleweed?

Stephan Kulow-3
Am 08.03.2016 um 06:24 schrieb Stephan Kulow:
> Am 07.03.2016 um 23:53 schrieb Alexander Melentev:
>> but some are horrible,but even if we all be really kind and say that
>> only 10% worth a report, doing so with 10 bugreports a day will take
>> me almost a year. So I would really like to have some other way to fix
>> those issues.
>>
> One bug report stating 10 horrible examples will be enough for us to get
> back to the SLE translators. Remember we pay them to do good
> translations, so we expect better than horrible.

To make that point clear: the 10 above is not a limit I meant to imply.
The 10 was just picked up from Alexander's mail :)

Greetings, Stephan

--
Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die
ganze Welt an Arsch offen hat, oder grad deswegn.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

12