From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/19376] regex reports "Invalid collation character" for Syriac characters
Date: Mon, 08 Jan 2024 10:43:49 +0000 [thread overview]
Message-ID: <bug-19376-716-Lv9YlCotrM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19376-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19376
Mike FABIAN <maiku.fabian at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
Assignee|unassigned at sourceware dot org |maiku.fabian at gmail dot com
--- Comment #8 from Mike FABIAN <maiku.fabian at gmail dot com> ---
According to my last comment, the only locales where this problem still occurs
are:
C.utf8
ar_SA.utf8
ja_JP.utf8
km_KH.utf8
ko_KR.utf8
lo_LA.utf8
sl_SI.utf8
th_TH.utf8
These are all locales which do not yet use
LC_COLLATE
% Copy the template from ISO/IEC 14651
copy "iso14651_t1"
...
The iso14651_t1_common file has been updated in 2017 to a much newer version
from 2016, which apparently fixed this problem except for the locales which
still do not use
copy "iso14651_t1"
I think that is good enough for the moment to close this bug here as FIXED.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-01-08 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19376-716@http.sourceware.org/bugzilla/>
2015-12-18 12:49 ` bonzini at gnu dot org
2015-12-18 15:06 ` t.rus76 at ya dot ru
2015-12-18 21:32 ` bonzini at gnu dot org
2015-12-18 21:32 ` joseph at codesourcery dot com
2015-12-18 21:32 ` carlos at redhat dot com
2015-12-18 21:32 ` carlos at redhat dot com
2024-01-08 10:37 ` maiku.fabian at gmail dot com
2024-01-08 10:43 ` maiku.fabian at gmail dot com [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-19376-716-Lv9YlCotrM@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).