[ruby-core:114933] [Ruby master Bug#10416] Create mechanism for updating of Unicode data files downstreams when we want
From:
"nobu (Nobuyoshi Nakada) via ruby-core" <ruby-core@...>
Date:
2023-10-01 16:47:35 UTC
List:
ruby-core #114933
Issue #10416 has been updated by nobu (Nobuyoshi Nakada).
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=3DLiner}/` as the comments in that file?
https://github.com/nobu/ruby/tree/unicode-15.1 is the former.
----------------------------------------
Bug #10416: Create mechanism for updating of Unicode data files downstreams=
when we want
https://bugs.ruby-lang.org/issues/10416#change-104804
* Author: duerst (Martin D=FCrst)
* Status: Open
* Priority: Normal
* Assignee: nobu (Nobuyoshi Nakada)
* ruby -v: ruby 2.2.0dev (2014-10-22 trunk 48092) [x86_64-cygwin]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
The current mechanism for updating Unicode data files will create the follo=
wing problem:
Downstream compilers/packagers will download Unicode data files ONE time (t=
hey may already have done so).
However, if they don't activate ALWAYS_UPDATE_UNICODE =3D yes, these files =
will never get updated, and they will stay on Unicode version 7.0 even if i=
n five years Unicode is e.g. on version 12.0.
On the other hand, if they activate ALWAYS_UPDATE_UNICODE =3D yes (and assu=
ming issue #10415 gets fixed), they constantly update to the latest version=
of Unicode. That's good for those who actually want this, but now what our=
current policy is.
What's missing is that we (Ruby core) can make sure downstream checkouts up=
date to a new Unicode version when we want then to do so (as we e.g. can do=
for other parts that are based on Unicode data, see e.g. https://bugs.ruby=
-lang.org/issues/9092), without sending an email to everybody and hoping th=
ey read and follow it.
[Currently, the only solution I know will work is the one pointed out by Yu=
i Naruse in https://bugs.ruby-lang.org/issues/10084#note-17, but I'm okay w=
ith any other solution.]
--=20
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/postorius/lists/ruby-c=
ore.ml.ruby-lang.org/