Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: eglibc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: vim (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8"
We track all i18n and l10n bugs under the ubuntu-translations project to
have a better oversight on them. Thanks a lot for the feedback, marked
it as Fix Released there.
** Changed in: ubuntu-translations
Status: Incomplete => Fix Released
--
You received this bug notification because you
This was fixed in language-selector, which is what I originally reported
it against. I'm not sure why it's marked as affecting ubuntu-
translations.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
** Changed in: ubuntu-translations
Importance: High => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charmap in locale name is wrong
To manage notifications about this b
>From the latest comments, I'm unsure about the status. Is there anything
else needed to fix this bug?
** Changed in: ubuntu-translations
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Not going to apply a large Ubuntu specific patch for this in langpack-
locales. This should get fixed in upstream glibc or not at all IMHO.
** Changed in: langpack-locales (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Branch linked: lp:~gunnarhj/ubuntu/lucid/gdm/lucid-backports_sec-
update
** Branch linked: lp:~gunnarhj/ubuntu/maverick/gdm/maverick-
backports_sec-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Fixes of this bug for Lucid and Maverick are now available in official
backports packages. To make Synaptic check for backports updates you can
do:
o System -> Administration -> Update Manager -> Settings...
o Select the "Updates" tab and check the "Unsupported updates" option.
More about Ubuntu
** Branch linked: lp:ubuntu/lucid-backports/gdm
** Branch linked: lp:ubuntu/maverick-backports/gdm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charmap in locale name is wrong
** Branch linked: lp:ubuntu/lucid-backports/language-selector
** Branch linked: lp:ubuntu/maverick-backports/language-selector
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" cha
** Branch linked: lp:~gunnarhj/ubuntu/lucid/language-selector/lucid-
backports
** Branch linked: lp:~gunnarhj/ubuntu/maverick/language-selector
/maverick-proposed
** Branch linked: lp:~gunnarhj/ubuntu/lucid/gdm/lucid-
backports_langfixes
** Branch linked: lp:~gunnarhj/ubuntu/maverick/gdm/maveric
** Branch unlinked: lp:~gunnarhj/language-selector/language-menu2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charmap in locale name is wrong
--
ubuntu-bugs mailing list
ubu
** Branch linked: lp:ubuntu/language-selector
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charmap in locale name is wrong
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
This bug was fixed in the package language-selector - 0.13
---
language-selector (0.13) natty; urgency=low
[ Gunnar Hjalmarsson ]
* LanguageSelector/gtk/GtkLanguageSelector.py:
- Ensure that main or origin country is included when country
specific options for a language
This bug was fixed in the package gdm - 2.32.0-0ubuntu8
---
gdm (2.32.0-0ubuntu8) natty; urgency=low
[ Gunnar Hjalmarsson ]
* debian/patches/36_language_environment_settings.patch:
- Use locale names with '.UTF-8' instead of '.utf8' when setting
the LC_MESSAGES environme
** Branch linked: lp:~gunnarhj/gdm/language-menu2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charmap in locale name is wrong
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
** Branch linked: lp:~gunnarhj/language-selector/language-menu2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charmap in locale name is wrong
--
ubuntu-bugs mailing list
ubunt
** Branch linked: lp:language-selector
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charmap in locale name is wrong
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
** Branch linked: lp:~ubuntu-desktop/gdm/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charmap in locale name is wrong
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
Copied from #ubuntu-devel, for the record:
Gunnar Hjalmarsson:
Thanks! Then, how about just replacing .utf8 with .UTF-8 to start with, and
introduce parsing of .../SUPPORTED later on, if the simplistic solution proves
to not suffice?
Colin Watson:
it would likely be an improvement, at least
Gu
I prefer the canonical names myself (i.e. en_IN rather than
en_IN.UTF-8), but either should be OK.
Parsing /usr/share/i18n/SUPPORTED is *easier* than parsing the
output of 'locale -a', and I think it's safer than trying to draw
inferences from details of the latter's output.
--
You received this
There seems to be a consensus of opinion that the encoding part of
locale names, that are assigned to the LANG or LC_* environment
variables, should be .UTF-8 rather than .utf8. I'm currently working on
language-selector and GDM with other language/locale related matters, so
I can include the neces
As from version 2.32.0-0ubuntu2, gdm (ubuntu) may assign locale name to
LC_MESSAGES.
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gdm (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
--
You received this bug notification because y
I agree that it makes sense to present UTF-8 as the primary spelling.
Note that I already said above that I agreed that language-selector
should be fixed. But it is clearly wrong to deny the existence of
locale aliases.
--
You received this bug notification because you are a member of Ubuntu
Bug
If we fix it for users and applications, say, the only visible one for
them is .UTF-8, then we can avoid many issues to deal with. It also
improves the compatibility when people connect to other distros (like
via ssh).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I am not saying that we should shift to use .utf8. I am saying that
when the locale ends up as .utf8 for one reason or another, applications
must not break.
This does not have to be an either/or thing! The primary name for the
locales are still generally .UTF-8 and should remain that way. But
l
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
On Fri, Jan 28, 2011 at 12:13:56PM -, 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 w
Referring to gettext document, which might be not really a standard but shows
their attitude about locale, they give .UTF-8 as example, but not mentioning
.utf8 at all.
http://www.gnu.org/software/hello/manual/gettext/Locale-Names.html#Locale-Names
I didn't do detailed research, but in some oth
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8"
Then that's a vim bug - I've opened a task for it.
** Also affects: vim (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charm
When I was using GVIM in China , it can not properly display Chinese
characters. It can only recognizes UTF-8, not utf8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charmap i
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charmap in locale name is wrong
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
Colin's right, of course -- my main issue with this isn't software
running locally, but remote systems. That's not trivial though: ssh into
some legacy machine, and they might not have compiled your locale at
all, or perhaps it's different (such as the case with en_IN). Of course,
that's not an Ubu
I still believe that the best option is to use UTF-8 as the primary
user-visible name in environment variables and such (since it's what's
in /usr/share/i18n/SUPPORTED), even though it's an alias, but to fix the
small handful of things that have trouble when you use one of the other
valid spellings
Yes, changing is risky. An alternative option is "fix" this in langpack-
locale, and try to make everywhere in the system to use "utf8" if any
problems occur. A temporary solution to use both utf8 and UTF-8 is of
course needed, and it should be just a work around. Such problem tends
to cost more an
But "utf8" has been the canonical form in eglibc for as long as I can
remember (at least ten years or so I believe). This isn't something
specific to Ubuntu. Changing it seems risky.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
The problem of "utf8" and "UTF-8" has been there for some time, and
there were arguments about it. Let's see:
$ locale -a
C
POSIX
zh_CN.utf8
zh_SG.utf8
# locale-gen
Generating locales...
zh_CN.UTF-8... up-to-date
zh_SG.UTF-8... up-to-date
Generation complete.
The problem is that we have mixe
** Also affects: eglibc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charmap in locale name is wrong
--
ubuntu-bugs maili
** Also affects: langpack-locales (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charmap in locale name is wrong
--
ubuntu-
** Also affects: ubuntu-translations
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charmap in locale name is wrong
--
ubuntu-bugs m
** Patch added: "Replace '.utf8' with 'UTF-8' in generated locale strings."
https://bugs.launchpad.net/bugs/666565/+attachment/1711201/+files/language-selector-localename.patch
--
"utf8" charmap in locale name is wrong
https://bugs.launchpad.net/bugs/666565
You received this bug notification
43 matches
Mail list logo
