From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: Cygwin <cygwin@cygwin.com>
Subject: Package Unicode-UCD 10 Outdated and New CLDR 36 and ICU 65 Just Announced
Date: Mon, 07 Oct 2019 15:52:00 -0000 [thread overview]
Message-ID: <fdfaf439-a9ed-0113-4e8f-f436acaed955@SystematicSw.ab.ca> (raw)
Hi folks,
I just looked at /usr/share/unicode/ucd/ and noticed the package is at version
10, a couple of versions back from current 12.1, issued earlier this year to
support changes for the new Japanese emperor Reiwa era:
http://blog.unicode.org/2019/05/unicode-12-1-en.html
and wonder whether other Unicode and UCD based packages are downloading,
maintaining, and using their own current copies, or still using outdated data.
I also noticed package unicode-cldr-emoji-annotation 30.0.3 appears to be a
couple of years out of date.
While on the Unicode site, I also noticed that CLDR 36 has just been released:
http://cldr.unicode.org/index/downloads/cldr-36
and ICU updated:
http://site.icu-project.org/download/65
and the latter site left lower sidebar gives the ongoing Schedule for all
projects, which may be useful as it estimates the annual Unicode and semiannual
CLDR and ICU release dates:
Schedule
2019-03
Unicode 12
CLDR 35
ICU 64(.1)
2019-04
New Japanese era:
Unicode 12.1
CLDR 35.1
ICU 64.2
2019-10
CLDR 36
ICU 65(.1)
2020-03
Unicode 13+bugs only
CLDR 37
ICU 66(.1)
2020-04
Unicode 13+features
CLDR 38
ICU 67(.1)
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
reply other threads:[~2019-10-07 15:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fdfaf439-a9ed-0113-4e8f-f436acaed955@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/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).