From: "Cygwin Gettext Maintainer" <Brian.Inglis@Shaw.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: gettext{,-devel,doc} {emacs,mingw64-x86_64}-gettext lib{gettextpo,asprintf}{0,-devel} libintl{8,-devel} 0.22.4
Date: Sun, 03 Dec 2023 11:23:54 -0700 [thread overview]
Message-ID: <20231203112354.8499-1-Brian.Inglis@Shaw.ca> (raw)
The following packages have been upgraded in the Cygwin distribution:
* gettext 0.22.4
* gettext-devel 0.22.4
* gettext-doc 0.22.4
* emacs-gettext 0.22.4
* libgettextpo0 0.22.4
* libgettextpo-devel 0.22.4
* libasprintf0 0.22.4
* libasprintf-devel 0.22.4
* libintl8 0.22.4
* libintl-devel 0.22.4
* mingw64-x86_64-gettext 0.22.4
A well integrated set of tools and documentation that provides a
framework for producing multi-lingual messages in programs.
Includes a set of conventions for writing programs to support message
catalogs, a directory and file naming organization for message catalogs,
a library for retrieving translated messages, and programs for handling
translatable and translated strings.
For changes since the previous Cygwin release, see below,
/usr/share/doc/gettext/NEWS after installation, or at:
https://savannah.gnu.org/news/index.php?group=gettext&limit=1
0.22.4 2023-11-19
* Bug fixes:
- AM_GNU_GETTEXT now recognizes a statically built libintl on macOS and AIX.
- Build fixes on AIX.
0.22.3 2023-10-04
* Portability:
- The libintl library now works on macOS 14. (Older versions of libintl
crash on macOS 14, due to an incompatible change in macOS.)
0.22.2 2023-09-19
* Bug fixes:
- The libintl shared library now exports again some symbols that were
accidentally missing. This bug was introduced in version 0.22.
0.22.1 2023-09-19
* Bug fixes:
- xgettext's processing of large Perl files may have led to errors
- "xgettext --join-existing" could encounter errors. These bugs were
introduced in version 0.22.
* Portability:
- Building on Android is now supported.
0.22 2023-06-17
* The base Unicode standard is now updated to 15.0.0.
reply other threads:[~2023-12-03 18:25 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=20231203112354.8499-1-Brian.Inglis@Shaw.ca \
--to=brian.inglis@shaw.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).