** Branch linked: lp:ubuntu/language-selector
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/926207
Title:
Set
This bug was fixed in the package accountsservice - 0.6.15-2ubuntu9
---
accountsservice (0.6.15-2ubuntu9) precise; urgency=low
* 0009-language-tools.patch: Also include LC_IDENTIFICATION, to comply to
how Ubiquity sets the locale. (LP: #926207)
*
** Branch linked: lp:ubuntu/accountsservice
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/926207
Title:
Set
** Tags removed: rls-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/926207
Title:
Set formats
** Tags added: rls-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/926207
Title:
Set formats related
** Branch linked: lp:~ubuntu-core-dev/localechooser/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
https://bugs.launchpad.net/bugs/926207
Title:
Set formats related LC_* variables when
** Branch linked: lp:ubiquity
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
https://bugs.launchpad.net/bugs/926207
Title:
Set formats related LC_* variables when applicable instead of
This bug was fixed in the package localechooser - 2.39ubuntu2
---
localechooser (2.39ubuntu2) precise; urgency=low
* Invert the set of locale categories set in case of a language/location
conflict, so we now set LC_NUMERIC, LC_TIME, LC_MONETARY, LC_PAPER,
LC_NAME,
** Also affects: language-selector (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
https://bugs.launchpad.net/bugs/926207
Title:
Set formats
It was intentionally I excluded LC_IDENTIFICATION in comment #7, since I
don't see how that category is related to regional formats. OTOH I agree
that it needs to be included to be consistent in not changing the
semantics.
Including LC_IDENTIFICATION also affects language-selector, so I added
yet
** Branch linked: lp:ubuntu/localechooser
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
https://bugs.launchpad.net/bugs/926207
Title:
Set formats related LC_* variables when applicable instead of
This bug was fixed in the package ubiquity - 2.10.2
---
ubiquity (2.10.2) precise; urgency=low
[ Colin Watson ]
* Fix test_misc.GrubDefaultTests.test_avoid_cdrom.
* Invert the set of locale categories set in case of a language/location
conflict, so we now set LC_NUMERIC,
To me it looks like different issues are unnecessarily mixed up here.
If I understand it correctly, the response to bug #590108 was to open a
way to use two locale names in a few specified cases. For instance:
If a user selects simplified Chinese as the language, followed by Taiwan
as the
In the current ubiquity installation LANG represents the region, and
LC_MESSAGES (and friends) the language. Thus LC_NUMERIC would default to
$LANG, i. e. the region. My gut feeling is that it should have been set
to the same value as LC_MESSAGES instead, as it's more related to the
displayed
Martin, Gunnar is proposing changing the semantics, and says that
accountservice.postinst has (effectively) already been changed in a way
that assumes that we have already done so.
Also, I chose my example carefully. What exact string value for a
region-oriented locale variable (never mind
Nobody apparently ever attempted to address my concern in bug 590108.
If the user says that they speak English and live in Switzerland, what
is the correct value for LC_NUMERIC? Please justify your answer
carefully and consider how the installer might make this judgement
automatically without
Al 03/02/12 19:06, En/na Gunnar Hjalmarsson ha escrit:
The eight formats related LC_* variables above are currently written to
/etc/default/locale and /etc/environment by language-selector, and to
~/.pam_environment by accountsservice. One question is whether it's
appropriate to 'pollute' the
The eight formats related LC_* variables above are currently written to
/etc/default/locale and /etc/environment by language-selector, and to
~/.pam_environment by accountsservice. One question is whether it's
appropriate to 'pollute' the environment with all of them.
In GNOME these environment
18 matches
Mail list logo
