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] combining characters (accents) misclassified as punct rather than alpha
Date: Wed, 13 Dec 2023 10:15:18 +0000 [thread overview]
Message-ID: <bug-31149-131-YDkznHeZps@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31149-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31149
--- Comment #2 from Vincent Lefèvre <vincent-srcware at vinc17 dot net> ---
(In reply to Florian Weimer from comment #1)
> Isn't the larger issue here that it's reasonable to expect that [[:alpha:]]
> matches a single letter as perceived by the user: an entire grapheme cluster
> comprising the base character(s), its associated combining characters and
> other marks. [...]
I don't think so. The functions iswctype(), iswalpha(), etc. take a single
code-point (type wint_t), and the regex(7) man page says:
Within a bracket expression, the name of a character class enclosed
in "[:" and ":]" stands for the list of all characters belonging to
that class. Standard character class names are:
alnum digit punct
alpha graph space
blank lower upper
cntrl print xdigit
These stand for the character classes defined in wctype(3). [...]
so that it is expected that [[:alpha:]] matches a single character, like the
above functions.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-12-13 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 15:53 [Bug localedata/31149] New: " vincent-srcware at vinc17 dot net
2023-12-13 10:01 ` [Bug localedata/31149] " fweimer at redhat dot com
2023-12-13 10:15 ` vincent-srcware at vinc17 dot net [this message]
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-YDkznHeZps@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).