From: "Cygwin libidn2 Maintainer" <Brian.Inglis@SystematicSW.ab.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: libidn2{,_0,-devel,-doc} mingw64-{x86_64,i686}-libidn2 2.3.4
Date: Sun, 30 Oct 2022 08:19:02 -0600 [thread overview]
Message-ID: <20221030081902.29820-1-Brian.Inglis@SystematicSW.ab.ca> (raw)
The following packages have been upgraded in the Cygwin distribution:
* libidn2 2.3.4
* libidn2_0 2.3.4
* libidn2-devel 2.3.4
* libidn2-doc 2.3.4
* mingw64-x86_64-libidn2 2.3.4
* mingw64-i686-libidn2 2.3.4
International Domain Name library encodes and decodes Internationalized
Domain Names implementing IETF IDN WG Stringprep, Punycode, IDNA2008,
and Unicode TR46 specifications.
Mingw packages provide MS VC RT-linked binaries, NOT Cygwin binaries,
for use with the mingw64-{x86_64,i686}-gcc cross compiler, installed in
/usr/{x86_64,i686}-w64-mingw32/sys-root/mingw/{bin,lib,include}/.
For more information see the project home page:
https://www.gnu.org/software/libidn/#libidn2
or the repo README:
https://gitlab.com/libidn/libidn2
Please see below or read /usr/share/doc/libidn2/NEWS after installation
for details of changes:
https://gitlab.com/libidn/libidn2/-/blob/master/NEWS
Noteworthy changes in release 2.3.4 (2022-10-23) [stable]
* Support for Unicode 15.0.0.
We now use Unicode.org's IDNA2008 tables rather than IANA's.
See <https://gitlab.com/libidn/libidn2/-/issues/112> and
<https://lists.gnu.org/archive/html/help-libidn/2022-10/msg00000.html>
for rationale, which can be summarized into
1) IANA are still on 2019-era Unicode version 12 and we wish to
support Unicode version 12-15,
2) consistency with some other implementations,
3) the only incompatibility related to U+19DA is deemed to have minor
real-world consequences.
Thus we break backwards compatibility for U+19DA in this release
compared against libidn2 0.11..2.3.3 thus reverting back to the
libidn2 <= 0.11 behaviour.
We decided to not bump ABI version and believe this is the best choice
going forward as well for minor internal non-API related ABI changes.
* Gnulib updated and now libunistring-optional is used.
This allows you to force libidn2 to use internal libunistring with the
following command: ./configure --with-included-libunistring
reply other threads:[~2022-10-30 14:21 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=20221030081902.29820-1-Brian.Inglis@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-announce@cygwin.com \
--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).