Re: Language and locale selection

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2013-07-19 at 16:30 -0400, Chris Lumens wrote:
> > I'm not sure "the vertical way" [1] is much better, but maybe it's just
> > some minor fix that is needed. Any suggestions?
> > 
> > [1]
> > http://vpodzime.fedorapeople.org/locale_selection_vertical_windows.png
> 
> I don't really like either.  To me, it's not at all clear what is being
> asked of me here.
> 
> I'm curious if this even needs to be at this early stage of
> installation.  Does this setting really affect anaconda?  Can it be
> pushed off to perhaps its own spoke while package installation is
> happening?
I believe it has all been anwered already, but let me some it up a bit:

1. We want the user to tell us the locale, not language, because the
locale is what we write out to config files, set to $LANG variable etc.
(see 3. for some details)

2. There may be different translations for different locales (e.g.
pt_BR/pt_PT or en_US/en_GB usually have separate translations). While
this already is resolved in the code we have now (with a single list)
because we list all translations we have, we also use external
libraries, that may have much more translations than we have. So while
we have only pt_BR, libxklavier or python's datetime module we use to
get month names have both pt_BR and pt_PT. Thus by letting user choose
the exact locale we may subsequently provide them better translations
even for the installation process.

3. $LANG and $LC_* variables are not as separate as they may seem to be.
One cannnot set $LANG and $LC_ALL to different values. Or more
precisely, it can be done, but $LC_ALL overrides $LANG in that case.
That means that by asking for locale we actually ask for language and
vice versa if we don't want to ask for each LC_ variable's value
separately.

4. There are many bugs and comments about wrong or missing
"languages" (more precisely locales) in our list. Recent examples are
Australian English missing and 'Punjabi (Pakistani)' listed instead of
'Punjabi (India)'. We have translations for Punjabi ('pa') and list
'Punjabi (Pakistani)' ('pa_PK') without an option to choose 'Punjabi
(India)' ('pa_IN').

Thus I believe we should allow users choose the exact locale and the
question is how to do that in an understandable and usable way. The
general question is how to deal with two-phase selection because having
all the locales in one list would make it very long.

-- 
Vratislav Podzimek

Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list




[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux