Whatever comments above, my stance is still the same. Iso-codes
references the standard, whatever the standard is : "good" or "wrong".
We even list "Taiwan, province of China" as name for Taiwan and, believe
me, this is way much more controversial than Bengali/Bangla.

In short, if you want us to use Bangla in iso-codes as the English name
for "bn", then get the standard changed.

As I explained already, Ubuntu maintainers are free to patch the package
to use whatever name they think is appropriate. I have no way to prevent
them from doing so, except 8 years experience telling me this is opening
a can of worms.

But, *I* will not patch iso-codes upstream. Neither in the released
tarball, nor in the Debian package. Debian will be right, whatever
"right" is. Ubuntu will be wrong, whatever "wrong" it is. That won't be
the first time that clumsy, short-term solutions are adopted in Ubuntu,
this seems to be the way development works there, sometimes. I really
don't care.

As a kind of compromise, I'll think about the possibility to add a
specific field we could name "common_name" in the ISO-639 XML file. This
is the trick we used for the "Taiwan" issue or the "Macedonia" issue in
ISO-3166. Maybe that could work as people wanting to use iso-codes and
play with alternatives (at the expense of other people not agreeing with
the use of alternatives to complain), to have the possibility of doing
it.

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

Title:
  Change name for bn-BD from 'Bengali(Bangladesh)' to
  'Bangla(Bangladesh)')

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/991002/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to