public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/63776] [C++11] Regex collate matching not working Date: Mon, 10 Nov 2014 18:26:00 -0000 [thread overview] Message-ID: <bug-63776-4-eIv1Gkl04K@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63776-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63776 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Tom Straub from comment #2) > Hi Tim, > > Okay, a program very similar to this using the Boost REGEX library and ICU > 4.55 works just fine with this. > > According to my understanding, the "char" data type and "std::string" > classes were specifically set up in C++11 to handle UTF-8 sequences. Nothing was done to char or std::string because they can already hold UTF-8 data. The new u8 literal prefix was added to produce UTF8-encoded string literals. > The "sequence of bytes" are actually valid UNICODE characters. Right, and if your source character set wasn't UTF-8 you could still initialize the std::string correctly with e.g. std::string s = u8"Jo\u00e3o M\u00e9ro\u00e7o"; > It is acting as if it is still in POSIX or C locale, since it doesn't > recognize the accented characters as "[:alpha:]" class. Yes, I don't know how it's supposed to work in <regex> but I agree there seems to be a bug. (In reply to Tim Shen from comment #1) > I don't know much about unicode support status in the standard library. > @Jon, can you put a comment? We're missing the facilities for converting between different unicode encodings which would allow us to convert multibyte char strings to wchar_t so that we can use the ctype<wchar_t>::is(ctype_base::mask, wchar_t) function to match non-ASCII characters. Maybe a workaround for now would be to detect when we reach the first byte of a UTF-8 character, read the rest of the multibyte character into a wchar_t and use ctype<wchar_t> for that. Or just wait for the rest of the ctype and codecvt features to be implemented.
next prev parent reply other threads:[~2014-11-10 18:26 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-07 18:39 [Bug c++/63776] New: " gnu-org at bignm dot com 2014-11-08 8:35 ` [Bug libstdc++/63776] " timshen at gcc dot gnu.org 2014-11-08 10:56 ` gnu-org at bignm dot com 2014-11-10 18:26 ` redi at gcc dot gnu.org [this message] 2015-01-20 11:05 ` gnu-org at bignm dot com 2015-01-20 11:10 ` gnu-org at bignm dot com 2015-01-20 13:08 ` redi at gcc dot gnu.org 2015-02-06 6:55 ` timshen at gcc dot gnu.org 2015-03-09 6:49 ` timshen at gcc dot gnu.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-63776-4-eIv1Gkl04K@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).