Thanks for your feedback.
The bug is that you use an unsupported locale ('C' and '*POSIX*' locales are
unsupported in language-selector, since there are no translations available for
those locales. Strings in applications can be in *any* language which uses the
ASCII charset, it's not necessrily English, although in the vast majority of
applications they are one of the English variants.
The current solution is to fall back to 'en_US' for such cases, but that
may overwrite your custom language settings, which you might have set
for specific reason.
The proper solution I would propose is to display a dialogbox to the user,
remind him that he uses an unsupported locale and ask him if he wants to switch
to the default system language or 'en_US' if the system language is also
unsupported.
The code may even try to parse the unsupported localecode for any hint what the
primary language it is (in case of en_POSIX_*, that would be 'en' -> English).
If the user decides to keep the unsupported locale, language-selector should do
nothing and just keep everything like it is.
Set the milestone to 'Later', since we are in string freeze already for
Lucid. This would be a problem to solve for Lucid+1.
** Changed in: language-selector (Ubuntu)
Importance: Undecided => Low
** Changed in: language-selector (Ubuntu)
Milestone: None => later
--
[jaunty] ValueError: too many values to unpack
https://bugs.launchpad.net/bugs/366951
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
