public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincent-srcware at vinc17 dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/31149] New: combining characters (accents) misclassified as punct rather than alpha
Date: Tue, 12 Dec 2023 15:53:21 +0000 [thread overview]
Message-ID: <bug-31149-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31149
Bug ID: 31149
Summary: combining characters (accents) misclassified as punct
rather than alpha
Product: glibc
Version: 2.37
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: vincent-srcware at vinc17 dot net
CC: libc-locales at sourceware dot org
Target Milestone: ---
Combining characters such as U+0301 COMBINING ACUTE ACCENT are misclassified as
punct, while this should be alpha.
With glibc 2.37 under Debian/unstable, I get for this character:
Property alnum : no
Property alpha : no
Property cntrl : no
Property digit : no
Property graph : yes
Property lower : no
Property print : yes
Property punct : yes
Property space : no
Property upper : no
Property xdigit: no
This affects grep: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27681 (where
it is said that the bug is in the GNU libc).
Corresponding Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868654
(which was reported on 2017-07-17 and hasn't got any activity yet).
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-12-12 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 15:53 vincent-srcware at vinc17 dot net [this message]
2023-12-13 10:01 ` [Bug localedata/31149] " fweimer at redhat dot com
2023-12-13 10:15 ` vincent-srcware at vinc17 dot net
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-31149-131@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).