public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/14094] Update locale data to Unicode 6.3
Date: Tue, 10 Jun 2014 14:38:00 -0000	[thread overview]
Message-ID: <bug-14094-131-snxIkrWVhx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14094-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=14094

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |carlos at redhat dot com

--- Comment #7 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Pravin S from comment #6)
> I have written script for checking backward compabitibility of new LC_CTYPE
> with old LC_CTYPE.
> 
> Script is available at https://github.com/pravins/glibc-i18n
> 
> Important thing for us presently is report generated by script. i.e. 
> 
> https://raw.githubusercontent.com/pravins/glibc-i18n/master/Report
> 
> While doing this also found in existing i18n file <U0D70>..<U0D75>; included
> twice.
> 
> % MALAYALAM/
>    <U0D66>..<U0D75>;<U0D70>..<U0D75>;/
> 
> Let me know if anything is missing.
> 
> In next step, i will check missing characters from LC_CTYPE 5.0.0 with
> LC_CTYPE 6.3.0 and confirm are these intentional changes at Unicode or
> something we are missing.
> 
> Will be ready with patch for updating LC_CTYPE next time.

Thanks Pravin! I think the missing step is to get these scripts checked into
glibc's script/ directory so that we have them in a central location with some
internal comments showing how to run the script. This way we can re-run them at
later stages to verify what's missing and stay in sync (say the release manager
runs it before a release).

Eventually we want a documented process here:
https://sourceware.org/glibc/wiki/Regeneration

Even if it's just "Run this script. Fix all warnings by hand" it would be a
good start.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-06-10 14:38 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 ` [Bug localedata/14094] Update locale data to Unicode 6.3 pravin.d.s at gmail dot com
2014-05-23 12:02 ` 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 [this message]
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-snxIkrWVhx@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).