On 7 March 2016 at 17:52, Luiz Fernando Ranghetti <elchevive68@gmail.com> wrote:
2016-03-07 11:51 GMT-03:00 Richard Brown <RBrownCCB@opensuse.org>:
On 7 March 2016 at 15:42, Stephan Kulow <coolo@suse.de> 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: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org