From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/16095] glibc should build an uz_UZ.UTF-8 locale, not only the Latin1 locales uz_UZ uz_UZ.iso88591
Date: Tue, 29 Oct 2013 10:11:00 -0000 [thread overview]
Message-ID: <bug-16095-716-fNuEsYREpt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16095-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16095
--- Comment #6 from Mike FABIAN <maiku.fabian at gmail dot com> ---
(In reply to joseph@codesourcery.com from comment #2)
> It's generally expected that any new locale will just be <locale>, using
> UTF-8, not <locale>.UTF-8 (that is, <locale>.UTF-8 is only, or at least
> primarily, for cases where <locale> is a pre-existing non-UTF-8 locale).
Which seems to be the case here, “uz_UZ” already exists and uses
ISO-8859-1 encoding, unfortunately.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-10-29 10:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 17:12 [Bug localedata/16095] New: " maiku.fabian at gmail dot com
2013-10-28 18:32 ` [Bug localedata/16095] " carlos at redhat dot com
2013-10-28 18:33 ` joseph at codesourcery dot com
2013-10-28 18:33 ` cjlhomeaddress at gmail dot com
2013-10-28 22:10 ` carlos at redhat dot com
2013-10-29 10:11 ` maiku.fabian at gmail dot com [this message]
2013-10-29 10:11 ` maiku.fabian at gmail dot com
2014-06-05 13:26 ` cvs-commit at gcc dot gnu.org
2014-06-05 13:27 ` schwab@linux-m68k.org
2014-06-13 12:29 ` fweimer at redhat dot com
2014-09-07 12:21 ` cvs-commit at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-16095-716-fNuEsYREpt@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).