public inbox for
 help / color / mirror / Atom feed
From: "Cygwin libidn Maintainer" <>
To: "Cygwin Announcements" <>
Subject: Updated: libidn{,12,-devel,-doc} mingw64-{x86_64,i686}-libidn 1.41
Date: Sat, 16 Jul 2022 15:21:59 -0600	[thread overview]
Message-ID: <> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1757 bytes --]

The following packages have been upgraded in the Cygwin distribution:

* libidn		1.41
* libidn12		1.41
* libidn-devel		1.41
* libidn-doc		1.41
* mingw64-x86_64-libidn	1.41
* mingw64-i686-libidn	1.41

Encode and decode Internationalized Domain Names implementing IETF IDN
WG Stringprep, Punycode and IDNA 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

For more information see the project home page:

or the repo README:

Please see below or read /usr/share/doc/libidn/NEWS after installation
for details of changes since the previous Cygwin release:

Noteworthy changes in release 1.41 (2022-06-25) [stable]

* Bump LT_REVISION for new release.
  It was mistakenly left at the same value since 1.38.

* Add version number related self-checks.

Noteworthy changes in release 1.40 (2022-06-20) [stable]

* lib: Bump STRINGPREP_VERSION to 1.40.
  It was mistakenly left at 1.38 in the 1.39 release.

Noteworthy changes in release 1.39 (2022-06-20) [stable]

* lib: Code detecting current locale broken since 1.36.
  The code always returned ASCII. The precise cause is complicated to
  track down but likely boils down to the new autotools/gettext
  bootstrapping sequence introduced in release 1.36. Reported by Богдан
  Пилипенко <>.

* maint: Java JAR archive no longer included in source tarball.

* Minor fixes: typos, makefiles, indentation, gnulib update, etc.

                 reply	other threads:[~2022-07-16 21:24 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).