public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pravin.d.s at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/14094] Update locale data to Unicode 6.3
Date: Fri, 23 May 2014 07:54:00 -0000 [thread overview]
Message-ID: <bug-14094-131-FqM51tpTAo@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14094-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14094
Pravin S <pravin.d.s at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Update locale data to |Update locale data to
|Unicode 6.1 |Unicode 6.3
--- Comment #3 from Pravin S <pravin.d.s at gmail dot com> ---
Rather than Uniocode 6.1, it should be Unicode 6.3.
Two files as mentioned in bug are
1. i18n (LC_CTYPE) (it used to be generated by gen-unicode-ctype.c, )
2. UTF-8 (it looks conversion from Unicode to UTF-8), i will find out
Are there any other files also involved in upgrading glibc localedata to
Unicode 6.1?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-05-23 7:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 20:28 [Bug localedata/14094] New: Update locale data to Unicode 6.1 jsm28 at gcc dot gnu.org
2012-05-11 3:26 ` [Bug localedata/14094] " bugdal at aerifal dot cx
2013-11-26 17:05 ` myllynen at redhat dot com
2014-02-18 9:24 ` pravin.d.s at gmail dot com
2014-05-21 11:11 ` allan at archlinux dot org
2014-05-23 7:54 ` pravin.d.s at gmail dot com [this message]
2014-05-23 12:02 ` [Bug localedata/14094] Update locale data to Unicode 6.3 joseph at codesourcery dot com
2014-05-23 13:20 ` pravin.d.s at gmail dot com
2014-06-10 9:38 ` pravin.d.s at gmail dot com
2014-06-10 14:38 ` carlos at redhat dot com
2014-06-11 3:49 ` pravin.d.s at gmail dot com
2014-06-19 10:28 ` pravin.d.s at gmail dot com
2014-06-21 19:10 ` [Bug localedata/14094] Update locale data to Unicode 7.0.0 pravin.d.s at gmail dot com
2014-06-25 11:02 ` fweimer at redhat dot com
2014-06-25 12:24 ` pravin.d.s at gmail dot com
2014-06-25 13:47 ` carlos at redhat dot com
2014-07-04 9:13 ` pravin.d.s at gmail dot com
2014-07-17 10:41 ` pravin.d.s at gmail dot com
2014-07-22 12:18 ` pravin.d.s at gmail dot com
2014-09-05 1:07 ` carlos at redhat dot com
2014-09-29 7:13 ` maiku.fabian at gmail dot com
2014-09-29 7:17 ` pravin.d.s at gmail dot com
2014-11-06 11:00 ` maiku.fabian at gmail dot com
2014-11-06 11:03 ` maiku.fabian at gmail dot com
2014-11-06 11:45 ` maiku.fabian at gmail dot com
2014-11-12 10:13 ` pravin.d.s at gmail dot com
2014-11-12 10:18 ` pravin.d.s at gmail dot com
2014-11-14 7:15 ` maiku.fabian at gmail dot com
2014-11-14 7:34 ` maiku.fabian at gmail dot com
2014-11-24 11:20 ` maiku.fabian at gmail dot com
2014-12-01 10:14 ` maiku.fabian at gmail dot com
2014-12-03 12:27 ` maiku.fabian at gmail dot com
2014-12-03 12:27 ` maiku.fabian at gmail dot com
2014-12-04 10:33 ` maiku.fabian at gmail dot com
2015-02-20 22:36 ` cvs-commit at gcc dot gnu.org
2015-02-21 0:06 ` aoliva at sourceware dot org
2015-02-21 20:24 ` aoliva at sourceware dot 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-14094-131-FqM51tpTAo@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).