[opensuse-factory] Use openSUSE own translations in Tumbleweed instead of SLE's
Hi, This problem has been there for a while, which is: We translators made translations for eg zypper, zypp, and many yast modules, but in the end the translations are not from svn.opensuse.org. I think those translations are from SLE. Because some of the translated strings look so weird that seem to be translated by outsourcing company that never know what Linux is. It introduced a lot of troubles, eg: Currently with zh_CN.UTF-8 locale, when you zypper dup: 是否继续？ [是/否/? 显示全部选项] (是): y 无效应答“y”。 [是/否/? 显示全部选项] (是): 是 Continue? [y/n/? show all options] (y): y Invalid answer "y". [y/n/? show all options] (y): 是 See? I have to type a Chinese "yes"! even in TTY which has no Chinese input method at all. The translations come from zypper.mo, but in my translated zypper.zh_CN.po: msgid "y/n" msgstr "y/n" See the difference? Please switch translations for Tumbleweed (even for Leap!) from unkonwn source to openSUSE user contributions. Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Mar 5, 2016 at 10:45 PM, Marguerite Su <i@marguerite.su> wrote:
Please switch translations for Tumbleweed (even for Leap!) from unkonwn source to openSUSE user contributions.
And it can't be solved by opening a few bug reports for Novell Language (seems to be a team), because there're too many... I think SLE team should consider filling their own translation database with openSUSE's, which is more accurate. Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Marguerite Su <i@marguerite.su> writes:
On Sat, Mar 5, 2016 at 10:45 PM, Marguerite Su <i@marguerite.su> wrote:
Please switch translations for Tumbleweed (even for Leap!) from unkonwn source to openSUSE user contributions.
And it can't be solved by opening a few bug reports for Novell Language (seems to be a team), because there're too many...
I think SLE team should consider filling their own translation database with openSUSE's, which is more accurate.
Thanks for reporting this! It looks serious. Nevertheless, we'd need a bug for it. A rather general one with one example would do. ATM, I'm inclined to withdraw the vendor provided translations for command-line tools, and let ship your community translations also on SLE. For zh_CN, I'm not sure about zh_TW, ja, and ko. -- Karl Eichwalder SUSE Linux GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Mar 7, 2016 at 8:48 PM, Karl Eichwalder <ke@suse.de> wrote:
Marguerite Su <i@marguerite.su> writes: Thanks for reporting this! It looks serious. Nevertheless, we'd need a bug for it. A rather general one with one example would do.
Yes...but you can't fix it...poor Karl...you have to look for a Chinese developer to fix it, and well I'm the best you have at hand currently... In the end, it means I have to review all translations for SLE. because there're too many bugs for it...because SLE users are IT professional who mainly use an English locale...some bugs hardly get found by them... Another funny example, in some part of SLE translation for zypper, the outsourcing company translated "pager" to "pager machine", that stuff we used to have before cellphone...but I never know zypper have any relationship with an old-time communication tool :-) That's why I said such thing can not be solved by opening a few bug reports... If someone can't even get the simplest thing right, how can you count on him for a much more different thing like s390, cluster, reipl or drbd translation? By the way, if you want to have SLE/openSUSE translations merged (I'd like to help you on this), please set up a place on svn...and let community professionals do it in the developer zone, don't push it to the user zone before it's done...
ATM, I'm inclined to withdraw the vendor provided translations for command-line tools, and let ship your community translations also on SLE. For zh_CN, I'm not sure about zh_TW, ja, and ko.
Well, for a short period...in the long run, I still like to be inspired by the SLE version to get a universal one for both. the oursourcing company was good about one thing: grammar :-) they can make a non-sense Chinese translation right in grammar :-) Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 07 Mar 2016 14:37:22 +0100, Marguerite Su wrote:
On Mon, Mar 7, 2016 at 8:48 PM, Karl Eichwalder <ke@suse.de> wrote:
Marguerite Su <i@marguerite.su> writes: Thanks for reporting this! It looks serious. Nevertheless, we'd need a bug for it. A rather general one with one example would do.
Yes...but you can't fix it...poor Karl...you have to look for a Chinese developer to fix it, and well I'm the best you have at hand currently...
The point is that we need a proper bug report as a reference, no matter how to fix -- to drop the whole wrong translation sets or to correct one by one. As Karl mentioned, the report doesn't necessarily point to each wrong text, but it can be a general one showing just one wrong example. Then we can decide what to do there.
In the end, it means I have to review all translations for SLE. because there're too many bugs for it...because SLE users are IT professional who mainly use an English locale...some bugs hardly get found by them...
Another funny example, in some part of SLE translation for zypper, the outsourcing company translated "pager" to "pager machine", that stuff we used to have before cellphone...but I never know zypper have any relationship with an old-time communication tool :-)
That's why I said such thing can not be solved by opening a few bug reports... If someone can't even get the simplest thing right, how can you count on him for a much more different thing like s390, cluster, reipl or drbd translation?
By the way, if you want to have SLE/openSUSE translations merged (I'd like to help you on this), please set up a place on svn...and let community professionals do it in the developer zone, don't push it to the user zone before it's done...
This is a good idea indeed.
ATM, I'm inclined to withdraw the vendor provided translations for command-line tools, and let ship your community translations also on SLE. For zh_CN, I'm not sure about zh_TW, ja, and ko.
Well, for a short period...in the long run, I still like to be inspired by the SLE version to get a universal one for both. the oursourcing company was good about one thing: grammar :-) they can make a non-sense Chinese translation right in grammar :-)
Heh, at least something is good there :) thanks, Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 7 March 2016 at 14:49, Takashi Iwai <tiwai@suse.de> wrote:
On Mon, 07 Mar 2016 14:37:22 +0100, Marguerite Su wrote:
On Mon, Mar 7, 2016 at 8:48 PM, Karl Eichwalder <ke@suse.de> wrote:
Marguerite Su <i@marguerite.su> writes: Thanks for reporting this! It looks serious. Nevertheless, we'd need a bug for it. A rather general one with one example would do.
Yes...but you can't fix it...poor Karl...you have to look for a Chinese developer to fix it, and well I'm the best you have at hand currently...
The point is that we need a proper bug report as a reference, no matter how to fix -- to drop the whole wrong translation sets or to correct one by one. As Karl mentioned, the report doesn't necessarily point to each wrong text, but it can be a general one showing just one wrong example. Then we can decide what to do there.
+1 As I said on the similar opensuse-translations mailinglist thread.. we really need those bug reports in order to turn these concerns into something we can actually act upon and track :) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Mar 7, 2016 at 10:55 PM, Richard Brown <RBrownCCB@opensuse.org> wrote:
On 7 March 2016 at 14:49, Takashi Iwai <tiwai@suse.de> wrote:
On Mon, 07 Mar 2016 14:37:22 +0100, The point is that we need a proper bug report as a reference, no matter how to fix -- to drop the whole wrong translation sets or to correct one by one. As Karl mentioned, the report doesn't necessarily point to each wrong text, but it can be a general one showing just one wrong example. Then we can decide what to do there.
+1
As I said on the similar opensuse-translations mailinglist thread.. we really need those bug reports in order to turn these concerns into something we can actually act upon and track :)
There's already one: https://bugzilla.opensuse.org/show_bug.cgi?id=968588 I also commented my reasons there. https://github.com/openSUSE/zypper/issues/93 And this is the upstream issue for zypper. I think we can concentrate the discussion on bugzilla. Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Karl Eichwalder -
Marguerite Su -
Richard Brown -
Takashi Iwai