From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/16095] New: glibc should build an uz_UZ.UTF-8 locale, not only the Latin1 locales uz_UZ uz_UZ.iso88591
Date: Mon, 28 Oct 2013 17:12:00 -0000 [thread overview]
Message-ID: <bug-16095-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16095
Bug ID: 16095
Summary: glibc should build an uz_UZ.UTF-8 locale, not only the
Latin1 locales uz_UZ uz_UZ.iso88591
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: maiku.fabian at gmail dot com
CC: libc-locales at sourceware dot org
Created attachment 7259
--> https://sourceware.org/bugzilla/attachment.cgi?id=7259&action=edit
0001-Support-UTF-8-locale-for-Uzbek-in-Latin-script.patch
Version: current master
There is no UTF-8 locale for Uzbek written in Latin script:
mfabian@ari:~
$ locale -a | grep ^uz
uz_UZ
uz_UZ.iso88591
uz_UZ.utf8@cyrillic
uz_UZ@cyrillic
mfabian@ari:~
$ LC_ALL=uz_UZ locale charmap
ISO-8859-1
mfabian@ari:~
$
I.e., although there is an UTF-8 locale for Uzbek written in Cyrillic
script, the Uzbek locales for Latin script are available only in
ISO-8859-1 encoding.
But Latin script is more common nowadays for Uzbek, see:
http://en.wikipedia.org/wiki/Uzbek_language#Writing_systems
CLDR also made Latin script the default for Uzbek recently, see
http://unicode.org/cldr/trac/ticket/6548 (Update country/language/pop for
Uzbek)
http://unicode.org/cldr/trac/changeset/9155 (cldrbug 6548: Updated
Uzbekistan Latin/Cyrillic? usage to better reflect modern education / usage.)
Therefore, it is not nice to use a if only a non-UTF-8 locale
can be used for Uzbek in Latin script, it is not nice to use
non-UTF-8 locales nowadays if one can avoid it.
Therefore, an uz_UZ.UTF-8 locale should be built as well.
Patch against current master attached.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2013-10-28 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 17:12 maiku.fabian at gmail dot com [this message]
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
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@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).