From: duerst@it.aoyama.ac.jp
To: ruby-core@ruby-lang.org
Subject: [ruby-core:89224] [Ruby trunk Feature#15182] Update extended grapheme cluster implementation for Unicode 11
Date: Mon, 01 Oct 2018 02:23:50 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-15182.20181001022349.e0135b986e4e281b@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15182.20181001022349@ruby-lang.org
Issue #15182 has been reported by duerst (Martin Dürst).
----------------------------------------
Feature #15182: Update extended grapheme cluster implementation for Unicode 11
https://bugs.ruby-lang.org/issues/15182
* Author: duerst (Martin Dürst)
* Status: Open
* Priority: Normal
* Assignee:
* Target version: 2.6
----------------------------------------
Reported by naruse (Yui NARUSE) at https://bugs.ruby-lang.org/issues/14802#change-74213:
The definition of extended grapheme cluster is changed in Unicode 11 (Unicode® Standard Annex #29
UNICODE TEXT SEGMENTATION revision 33: https://www.unicode.org/reports/tr29/tr29-33.html)
This affects Regexp /\X/ which is hardcoded in node_extended_grapheme_cluster() in regparse.c.
```
( CRLF
| Prepend*
( RI-sequence | Hangul-Syllable | !Control )
( Grapheme_Extend | SpacingMark )*
| . )
```
```
crlf
| Control
| precore* core postcore*
```
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2018-10-01 2:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15182.20181001022349@ruby-lang.org>
2018-10-01 2:23 ` duerst [this message]
2018-12-07 9:57 ` [ruby-core:90363] [Ruby trunk Feature#15182][Closed] Update extended grapheme cluster implementation for Unicode 11 duerst
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-15182.20181001022349.e0135b986e4e281b@ruby-lang.org \
--to=ruby-core@ruby-lang.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).