Comment 12 for bug 666565

if we shift to use utf8, what about other distro still use UTF-8? are
we going to ignore the interoperability. In addition, how can we
convince all other user space applications adopt utf8?
I found that UTF-8 is till being used in eglibc, so whats the
advantage to use utf8?

On Fri, Jan 28, 2011 at 8:36 PM, Colin Watson <email address hidden> wrote:
> On Fri, Jan 28, 2011 at 12:13:56PM -0000, Aron Xu wrote:
>> No, it wouldn't be. I think any application that doesn't work with
>> .UTF-8 should be a bug, but not for it doesn't work with .utf8.
>
> I entirely disagree.  .utf8 is a valid spelling of the locale and it's a
> bug for applications to fail to work with it.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/666565
>
> Title:
>  "utf8" charmap in locale name is wrong
>
> Status in Ubuntu Translations:
>  Triaged
> Status in “eglibc” package in Ubuntu:
>  New
> Status in “langpack-locales” package in Ubuntu:
>  New
> Status in “language-selector” package in Ubuntu:
>  New
> Status in “vim” package in Ubuntu:
>  New
>
> Bug description:
>  Binary package hint: language-selector
>
>  LanguageSelector/macros.py explicitly sets the charmap part of locale
>  strings to "utf8" - it should be set to "UTF-8" instead. This is
>  relevant because not all systems alias locale names with the former to
>  the latter, and compatibility with those systems is broken.
>
>  Rationale for this change is that the 'locales' package uses the uppercase hyphenated format everywhere, even going as far as replacing '.utf8' with it in one case:
>  % dpkg -L locales | xargs grep '\.utf8'
>  /usr/sbin/locale-gen:    elif [ $IS_LANG = no ] && L=`grep "^${1/%.utf8/.UTF-8} " /usr/share/i18n/SUPPORTED`; then
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu-translations/+bug/666565/+subscribe
>