ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: duerst via ruby-core <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: duerst <noreply@ruby-lang.org>
Subject: [ruby-core:119130] [Ruby master Feature#19908] Update to Unicode 15.1
Date: Thu, 12 Sep 2024 03:21:28 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-109725.20240912032110.4@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-19908.20231002065545.4@ruby-lang.org>

Issue #19908 has been updated by duerst (Martin Dürst).


hsbt (Hiroshi SHIBATA) wrote in #note-8:
> Unicode 16.0 has been released.

> Should we move this instead of 15.1?

I think it's more prudent to do 15.1 first, then 16.0. I hope to be able to work on this soon. I created a separate issue for 16.0.

----------------------------------------
Feature #19908: Update to Unicode 15.1
https://bugs.ruby-lang.org/issues/19908#change-109725

* Author: nobu (Nobuyoshi Nakada)
* Status: Assigned
* Assignee: duerst (Martin Dürst)
----------------------------------------
The Unicode 15.1 is released.

The current enc-unicode.rb seems to fail because of `Indic_Conjunct_break` properties with values.

I'm not sure how these properties should be handled well.
`/\p{InCB_Liner}/` or `/\p{InCB=Liner}/` as the comments in that file?
https://github.com/nobu/ruby/tree/unicode-15.1 is the former.



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/

  parent reply	other threads:[~2024-09-12  3:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02  6:55 [ruby-core:114936] " nobu (Nobuyoshi Nakada) via ruby-core
2023-10-02 14:06 ` [ruby-core:114939] " Игорь Пятчиц via ruby-core
2023-12-26  6:52 ` [ruby-core:115899] " duerst via ruby-core
2023-12-26 11:42 ` [ruby-core:115906] " duerst via ruby-core
2024-01-06 21:28 ` [ruby-core:116056] " janosch-x via ruby-core
2024-01-09  1:25 ` [ruby-core:116099] " duerst via ruby-core
2024-09-12  1:56 ` [ruby-core:119128] " hsbt (Hiroshi SHIBATA) via ruby-core
2024-09-12  3:21 ` duerst via ruby-core [this message]
2024-09-12  3:53 ` [ruby-core:119131] " hsbt (Hiroshi SHIBATA) via ruby-core
2025-01-01 15:06 ` [ruby-core:120460] " ima1zumi (Mari Imaizumi) via ruby-core

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=redmine.journal-109725.20240912032110.4@ruby-lang.org \
    --to=ruby-core@ml.ruby-lang.org \
    --cc=noreply@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 NNTP newsgroup(s).