The GNU gettext package contains
* tools for internationalization, enabling a programmer to make their package
"speak" to the users in their specific language,
* tools for localization, enabling a translator to initialize, check, and
review the message translations that they provide for a package,
* runtime libraries; in particular, a libintl library that implements the
C function gettext() portably, in a glibc-compatible way.
It is now available in version 0.24.
==== New in 0.24 ====
# Programming languages support:
* JavaScript:
- xgettext now parses recursive JSX expressions correctly.
* Rust:
- xgettext now supports Rust.
- 'msgfmt -c' now verifies the syntax of translations of Rust format
strings.
- A new example 'hello-rust' has been added.
* C:
- A new example 'hello-c-http' has been added, showing the use of
GNU gettext in a multithreaded web server.
* C++:
- A new example 'hello-c++-gnome3' has been added.
* Ruby:
- A new example 'hello-ruby' has been added.
# Improvements for maintainers:
* When xgettext creates the POT file of a package under Git version control,
the 'POT-Creation-Date' in the POT file usually no longer changes
gratuitously each time the POT file is regenerated.
# Caveat maintainers:
* Building the po/ directory now requires GNU make on specific platforms:
macOS, Solaris, AIX.
==== Download ====
Here are the compressed sources:
https://ftp.gnu.org/gnu/gettext/gettext-0.24.tar.gz (27MB)
https://ftp.gnu.org/gnu/gettext/gettext-0.24.tar.lz (7.5MB)
https://ftp.gnu.org/gnu/gettext/gettext-0.24.tar.xz (8.0MB)
Here are the GPG detached signatures:
https://ftp.gnu.org/gnu/gettext/gettext-0.24.tar.gz.sig
https://ftp.gnu.org/gnu/gettext/gettext-0.24.tar.lz.sig
https://ftp.gnu.org/gnu/gettext/gettext-0.24.tar.xz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
Here are the SHA1 and SHA256 checksums:
File: gettext-0.24.tar.gz
SHA1 sum: 4a1731caf2ec86ca4481f754974f31ac6dc36f8a
SHA256 sum: c918503d593d70daf4844d175a13d816afacb667c06fba1ec9dcd5002c1518b7
File: gettext-0.24.tar.lz
SHA1 sum: 469acd774ee7a76b8146464a7e53e10ac9a99d94
SHA256 sum: 0eb4153c3fc066d050242541156e8fd1ad74e80e4c08c2cc9f426e68e3d98015
File: gettext-0.24.tar.xz
SHA1 sum: 82864d432c222ea57ef87b3c2e07d451101a8aea
SHA256 sum: e1620d518b26d7d3b16ac570e5018206e8b0d725fb65c02d048397718b5cf318
Use a .sig file to verify that the corresponding file (without the
.sig suffix) is intact. First, be sure to download both the .sig file
and the corresponding tarball. Then, run a command like this:
gpg --verify gettext-0.24.tar.gz.sig
The signature should match the fingerprint of the following key:
pub ed25519 2025-01-28 [SC]
E0FF BD97 5397 F77A 32AB 76EC B630 1D9E 1BBE AC08
uid Bruno Haible (Free Software Development) <br...@clisp.org>
If that command fails because you don't have the required public key,
or that public key has expired, try the following commands to retrieve
or refresh it, and then rerun the 'gpg --verify' command.
gpg --recv-keys B6301D9E1BBEAC08
As a last resort to find the key, you can try the official GNU
keyring:
wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpg
gpg --keyring gnu-keyring.gpg --verify gettext-0.24.tar.gz.sig
