[Bug 1070581] Re: Name of the language spoken in Bangladesh

[Michael Terry]

Much like bug 991002, this is a situation where Ubuntu would not enjoy
getting ahead of its upstream (in this case, glibc).  I've filed a bug
and will file a patch (attributed to you) with them:
http://sourceware.org/bugzilla/show_bug.cgi?id=14925

Once they fix it upstream, Ubuntu will have to sync that localedata into
langpack-locales.

** Bug watch added: Sourceware.org Bugzilla #14925
   http://sourceware.org/bugzilla/show_bug.cgi?id=14925

** Also affects: glibc via
   http://sourceware.org/bugzilla/show_bug.cgi?id=14925
   Importance: Unknown
       Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1070581

Title:
  Name of the language spoken in Bangladesh

Status in The GNU C Library:
  Unknown
Status in “langpack-locales” package in Ubuntu:
  In Progress

Bug description:
  When querying nl_langinfo() for the language name of bn_BD.UTF-8, it
  outputs the string "BengaliBangla", which of course looks a little
  weird. The source file locales/bn_BD states the language
  "Bengali/Bangla" with a slash.

  A better name would be just "Bangla", since that's the official name
  of the language spoken in Bangladesh, and the native Bangla speakers
  seems to prefer it; please see bug #991002. The iso-codes package will
  soon provide translations of the name "Bangla", bug AFAIK noone
  provides translations of the string "Bengali/Bangla".

  But at least the bn_BD locale should be corrected so nl_langinfo()
  returns the string "Bengali/Bangla" including the slash.

  Two alternative patches have been attached to this bug report. One
  just escapes the slash ("Bengali//Bangla") to address the slash issue.
  The other patch changes the language in both bn_BD and bn_IN to
  Bangla. I involve bn_IN, since it's confusing in e.g. lists of locales
  that two locales use different English names for the same language.

  Please pick the patch that fits best. ;-)

  Let's talk about possible forwarding upstream when it has been decided
  which route to take.

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