From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/14010] Serious omissions in alphabetic character class
Date: Thu, 04 Dec 2014 10:34:00 -0000 [thread overview]
Message-ID: <bug-14010-716-AK5eQSMYLq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14010-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14010
Mike FABIAN <maiku.fabian at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |maiku.fabian at gmail dot com
Resolution|--- |DUPLICATE
--- Comment #6 from Mike FABIAN <maiku.fabian at gmail dot com> ---
(In reply to Rich Felker from comment #5)
> On Fri, Oct 25, 2013 at 03:19:28PM +0000, joseph at codesourcery dot com
> wrote:
> > The connection is that they all (and bug 16061) need someone to act as
> > glibc's character set / Unicode expert and do a proper analysis of the
> > issues involved and the current state of this data in glibc.
>
> My view is that I don't think it requires a collation expert to handle
> the fixing of the alphabetic class and/or updating the character class
> data to latest Unicode. Collation is a much more specialized expertise
> requirement.
https://sourceware.org/bugzilla/show_bug.cgi?id=14094#c33 amd following
comments address the problem with the alphabetic class and
updating the character classes to the latest Unicode.
So I think we can mark this bug here as a duplicate of bug#14094.
*** This bug has been marked as a duplicate of bug 14094 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-12-04 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 4:22 [Bug localedata/14010] New: " bugdal at aerifal dot cx
2012-09-21 23:46 ` [Bug localedata/14010] " bugdal at aerifal dot cx
2012-09-23 22:39 ` joseph at codesourcery dot com
2013-10-25 20:32 ` myllynen at redhat dot com
2013-10-25 20:34 ` bugdal at aerifal dot cx
2013-10-25 20:34 ` joseph at codesourcery dot com
2013-10-25 20:34 ` bugdal at aerifal dot cx
2014-06-25 12:09 ` fweimer at redhat dot com
2014-12-04 10:34 ` maiku.fabian at gmail dot com [this message]
2020-04-15 13:51 ` meave390 at gmail dot com
2020-04-15 14:02 ` meave390 at gmail dot com
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-14010-716-AK5eQSMYLq@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).