Bug 557768

Summary: Limit language selection to "SLE11 tier-1" languages
Product: [openSUSE] openSUSE 11.2 Reporter: Klaus Kämpf <kkaempf>
Component: WebYaSTAssignee: Josef Reidinger <jreidinger>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P2 - High CC: jreidinger, jsuchome
Version: RC 2   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Klaus Kämpf 2009-11-23 15:32:36 UTC
The selection list of the language module is too big. Limit it to the SLE11 tier-1 languages
Comment 1 Klaus Kämpf 2009-11-25 10:27:42 UTC
This should be easy to fix I hope
Comment 2 Josef Reidinger 2009-11-25 13:40:02 UTC
schubi - If you change it then please also inform me, as I use also I18n.supported_languages so I must change it too.
Comment 3 Stefan Schubert 2009-11-25 17:12:51 UTC
We have had a discussion on IRC. It is not clear which way we are going.
Klaus could you please assists here ?

[17:54] <jreidinger> schubi: How do you want see fix? Hard-coded list of supported locale?
[17:55] <schubi> jreidinger: I would prefer the same solution as the yast2-language module does already do. (Have seen the UI only the primary languages)
[17:56] <schubi> Currently I do not know how it works "internally"
[17:57] <jreidinger> so change is that it show only primary languages? I think in webyast we don't have much national modification except en
[17:59] <schubi> I would say yes. I think Klaus intention is to decrease the count of languages and as we are based on SLES11 the amount should be the same as they are displayed in yast2-language.
[18:03] <schubi> jreidinger: What i do not understand is, isn't the same list as the "available languages" while the restservice call ?
[18:06] <jreidinger> schubi: I think not, it is reduced one...for this reason I think we should wait to klaus that he confirm if new list is still problem
[18:07] <jreidinger> but of course if we get predefined list of supported languages, then it is not problem to show only that list...is it somewhere availabla for SLES?
[18:07] <schubi> jreidinger: OK, I will ask him again tomorrow.
[18:08] <jreidinger> schubi: If we still need to reduce it I prefer predefined list now and vendor settings solution after release (as vendor could create new localization and add it). Then we just replace I18n.supported_languages by that list
Comment 4 Jiří Suchomel 2009-11-26 07:33:41 UTC
Josef, Tier 1 languages are not those shown in "yast2 language". YaST shows all languages that have translation support in YaST itself.

I'm not sure about the correct list for SLES, but e.g. in openSUSE manual we are stating this:

"Tier 2 languages are all but the tier 1 languages (English, French, German, Italian, Spanish, Brazilian Portuguese, simplified and traditional Chinese, Japanese, and Czech)."


Anyway, you need a fixed subset of languages.
Comment 5 Josef Reidinger 2009-11-26 11:19:58 UTC
From my point of view. It is easy to implement it (replace one method by own with predefined list). But it is not clear which langauges and which locale is sufficient. So I suggest don't include it to GMC.
Comment 6 Jiří Suchomel 2009-11-27 10:10:24 UTC
(In reply to comment #4)

> "Tier 2 languages are all but the tier 1 languages (English, French, German,
> Italian, Spanish, Brazilian Portuguese, simplified and traditional Chinese,
> Japanese, and Czech)."

SLES 11 license translations are:

ar
cs
de
es
fr
hu
it
ja
ko
nl
pl
pt_BR
ru
sv
zh_CN
zh_TW

So there are more of than than in a list from comment 4. If you want only those listed in comment 4, there are


cs
de
es
fr
it
ja
pt_BR
zh_CN
zh_TW

Don't forget en_US (it's not a translation, so not listed in a translate list)
Comment 8 Josef Reidinger 2009-11-27 11:31:59 UTC
working on it
Comment 9 Jiří Suchomel 2009-11-27 13:53:34 UTC
I've installed yast2-webclient-language-0.0.11 and yast2-webclient-0.0.26 into RC4 and indeed, language list is shortened to the first list shown in comment 6.
Comment 10 Josef Reidinger 2009-11-27 15:07:06 UTC
fixed package has been sent to stable