From: "Cygwin Gettext Maintainer" <Brian.Inglis@SystematicSW.ab.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: gettext{,-devel,doc} emacs-gettext lib{gettextpo,asprintf}{0,-devel} libintl{8,-devel} mingw64-{x86_64,i686}-gettext 0.21.1
Date: Sat, 29 Oct 2022 23:00:11 -0600 [thread overview]
Message-ID: <20221029230011.2264-1-Brian.Inglis@SystematicSW.ab.ca> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
The following packages have been uploaded to the Cygwin distribution:
* gettext 0.21.1
* gettext-devel 0.21.1
* gettext-doc 0.21.1
* emacs-gettext 0.21.1
* libgettextpo0 0.21.1
* libgettextpo-devel 0.21.1
* libasprintf0 0.21.1
* libasprintf-devel 0.21.1
* libintl8 0.21.1
* libintl-devel 0.21.1
* mingw64-x86_64-gettext 0.21.1
* mingw64-i686-gettext 0.21.1
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 version, see below,
/usr/share/doc/gettext/NEWS after installation, or the link:
https://git.savannah.gnu.org/gitweb/?p=gettext.git;f=NEWS;a=blob
Version 0.21.1 - October 2022
* The base Unicode standard is now updated to 14.0.0.
* Portability:
- Building on macOS 11/arm64 is now supported.
- Building on Linux/powerpc64le with glibc ≥ 2.35 is now supported.
* Runtime behaviour:
- On AIX, locale names with a script or with an uppercase language are now
supported.
For example, sr_Cyrl_RS.UTF-8 is treated like sr_RS.UTF-8@cyrillic, and
EN_US.UTF-8 is treated like en_US.UTF-8.
reply other threads:[~2022-10-30 5:04 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=20221029230011.2264-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).