[Bug 1560577] Re: Confusing new locale-gen behavior

Gunnar Hjalmarsson 1560577 at bugs.launchpad.net
Tue Apr 5 18:33:37 UTC 2016


I encountered another issue at <http://askubuntu.com/q/753516>: If you
for instance pass the argument "en_IN.UTF-8", locale-gen currently sees
it as unsupported, since the real name in SUPPORTED is just "en_IN". New
locales tend to be UTF-8 only, and I think locale-gen should accept
arguments with the codeset appended in these cases.

@Adam: I made a patch out of my proposed changes. If other glibc stuff
is on its way in before final freeze, you may want to consider it
together with them. Otherwise I think the proposed changes would
motivate a separate upload.

** Patch added: "glibc_locale-gen.patch"
   https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1560577/+attachment/4624971/+files/glibc_locale-gen.patch

** Changed in: glibc (Ubuntu)
       Status: Confirmed => In Progress

** Changed in: glibc (Ubuntu)
     Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1560577

Title:
  Confusing new locale-gen behavior

Status in glibc package in Ubuntu:
  In Progress

Bug description:
  When the locales package was provided by the langpack-locales source
  package, you could call locale-gen with arguments. Examples:

  sudo locale-gen en_US.UTF-8
  (to generate that locale only)

  sudo locale-gen --purge
  (to purge all existing locales and create all locales)

  With the locales package provided by glibc, the equivalent to the
  latter seems to be:

  sudo locale-gen

  What's problematic is that if you add an argument (any argument), the
  existing locales seem to be purged, but nothing is generated. I'd
  consider this to be a pretty serious regression, which will likely
  result in locale issues for many users, if something isn't done to fix
  it. I'm not sure how to best deal with the problem, though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1560577/+subscriptions



More information about the foundations-bugs mailing list