Translations are always from SLE

[marguerite]

Hi,

see: http://lists.opensuse.org/opensuse-factory/2016-03/msg00063.html

translations from SLE contain serious bugs that hotkeys were all translated, which caused CJK users have to input some CJK characters for "yes/no/abort/retry..." stuff when there's no input method for CJK existing in TTY.

and I think it's also a packaging bug because I can see you have two branches of translations, but in Tumbleweed zypper uses translations from SLE, which may not what you want.

[marguerite]

PS: I suggest we do not allow translation for hotkeys. because then dual-language speaking people have to remember two sets of hotkeys especially when, for fake example, in some certain languages, "retry" begin with "c", "cancel" begin with "r", which will be very confusing.

no matter to say leaving hotkeys to translator means you count on translators who have no programming experience to design a set of hotkeys that do not conflict with each other. especially for SLE products. I think you guys do not translate yourself but outsource it to "professional companys" that are full of grammar experts who never use or know Linux.

[mlandres]

@coolo - How to solve this? You asked to use the SLE translations as primary set for openSUSE as well (especially for LEAP). Change TW back to use the commuity translations?

[mlandres]

This is partially a duplicate of bsc#968588 - Tumbleweed's zypper uses translations from SLE.

The decision there is to continue to maintain one translation set per zypper code branch (and not per distribution). Currently this set is created by merging SLE and community sources, preferring SLE translations if available. The log term goal is of course to unify those different translation sources.

The issue of translated hotkeys will be handled here.

[marguerite]

@mlandres well, I don't want to act like I'm against coolo's decision, there are two ways for the merge:

Let the translator coordinators/regional community "leaders" (if reachable) to choose:

• if want the merge. eg, I can't represent German speaking people, I can only say, for Chinese, community version is better and bug free than SLE version.
• which set should be preferred. I know you guys want to "perfer SLE translation if available" because you think those translation are more complete and professional, but whether good or not can only be judged by the actual users, not by people who know nothing about that language, or who don't use Linux at all. As I see, the SLE version of translation for Chinese is just complete, not good. I see multiple times that a "pager" is translated to "pager machine (the one we used to have before cellphone)" in zypper (I can report over 100 bugs if I want, but that work equals to that I have to re-translate SLE)

And that "long term goal" can not be achieved if SLE version is preferred...because:

• SLE doesn't provide some languages that have only less than 10 users, right? eg, Tajik, Persian, Malay, do you know what are they :-) ? Translations for SLE and openSUSE will never be the same in languages.
• And to use "unkonwn source" to replace someone's hard work is just not good...this will get community contributors pissed off...eg: in this case, if you still force to use SLE version of translation (no matter to say source codes for that are not available to me yet, there are also no guides on how to translate for SLE on our wiki either), I will be criticized by Chinese community users that I didn't get my work done right, well to maintain my good credit I have to fix thousands of translations that the primary goal for them were not to serve for me but for a distribution that I can' afford.

Actually you can do things in this way, for those language branch that have active contributors, use SLE version to fill the blanks that community contributors didn't fill, that let the community users to find the remaining bugs. in the way, you will get a better translation.

PS: the hotkey problem can't be solved that easy, because there're too many of them besides other bugs, see my previous example, because people who use SLE are mainly a few professional SAs who use an English system...

Marguerite

[marguerite]

I also comment on the bug report with much more careful wording and reasoning.

[mlandres]

Fixed by moving translations to weblate.