ubuntu-translations-coordinators team mailing list archive

[Launchpad Bug Tracker <926207@xxxxxxxxxxxxxxxxxx>]

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, LC_TIME, LC_MONETARY, LC_PAPER,
    LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT, and LC_IDENTIFICATION
    instead (LP: #926207).
  * Automatic update of included source packages: localechooser 2.39ubuntu2.

  [ Brian Murray ]
  * UTF-8-encode debug messages which are written to stderr (LP: #960278)
 -- Colin Watson <cjwatson@xxxxxxxxxx>   Fri, 23 Mar 2012 18:00:36 +0000

** Changed in: ubiquity (Ubuntu)
       Status: Triaged => Fix Released

-- 
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
  LC_MESSAGES, LC_CTYPE and LC_COLLATE

Status in Ubuntu Translations:
  New
Status in “accountsservice” package in Ubuntu:
  Triaged
Status in “language-selector” package in Ubuntu:
  New
Status in “localechooser” package in Ubuntu:
  Fix Released
Status in “ubiquity” package in Ubuntu:
  Fix Released

Bug description:
  Up to Oneiric the LANG environment variable has in Ubuntu been
  considered to represent the regional formats. Hence, in cases where a
  user wants to use different locales for language respective formats,
  LC_MESSAGES, LC_CTYPE and LC_COLLATE has been set explicitly.
  Consequently the installer has set those three variables in
  /etc/default/locale when applicable.

  In Precise we are making a conceptual change, meaning that LANG now is
  considered to represent the display language, and the formats related
  LC_* variables are set explicitly when needed to distinguish between
  language and formats. As mentioned at bug #590108, this is the
  rationale for the switch:

  * It's how GNOME does it in g-c-c, and considering that we are moving
    towards replacing the language-selector UI with "Region and Language"
    in g-c-c, it would eliminate one of the current differences in
    approach between Ubuntu and GNOME.

  * There seems to be quite a few desktop apps/tools, or parts of apps,
    that ignore both LANGUAGE and LC_MESSAGES for the display language,
    and let LANG solely determine the display language. (My LANG usually
    contains a Swedish locale, while my display language is English, and
    I often see Swedish translations in dialogs and menus.)

  * Some distributions may prefer the simplistic approach to equal l10n
    with simply picking a locale name and assigning it to LANG. If we
    would switch to let LANG represent the language, the LANG variable
    would be used for language all over, which would reduce the risk for
    confusion with respect to locale/language settings.

  Changes reflecting this switch have recently been uploaded to accountsservice and language-selector. Previous settings in /etc/default/locale and /etc/environment of LC_MESSAGES, LC_CTYPE and LC_COLLATE are deleted via accountsservice.postinst.
  http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/accountsservice/precise/view/head:/debian/accountsservice.postinst

  For fresh installs that code is skipped, so it's important that the
  corresponding changes are made to the installer:

    In cases when the user makes choices at installation meaning that the
    locale for display language differs from the locale for regional
    formats, the installer should set LC_NUMERIC, LC_TIME, LC_MONETARY,
    LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and
    refrain from setting LC_MESSAGES, LC_CTYPE and LC_COLLATE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/926207/+subscriptions