From: "Ludovic Courtès" <ludo@gnu.org>
To: Guix Devel <guix-devel@gnu.org>
Cc: andreas@enge.fr, janneke@gnu.org
Subject: [Bruno Haible] GNU gettext 0.23.1 is released
Date: Wed, 08 Jan 2025 09:55:00 +0100 [thread overview]
Message-ID: <87tta9wuqj.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 174 bytes --]
Hello,
Sharing this message about upgrading Gettext, with Bruno’s permission (I
believe gettext should be in the scope of the ‘core-packages’ team).
Ludo’.
[-- Attachment #2: Type: message/rfc822, Size: 1260 bytes --]
From: Bruno Haible <bruno@clisp.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Subject: GNU gettext 0.23.1 is released
Date: Tue, 31 Dec 2024 15:40:33 +0100
Available at
https://ftp.gnu.org/gnu/gettext/gettext-0.23.1.tar.gz
New in 0.23.1:
* Bug fixes:
- Building with libxml2 >= 2.12.0 and gcc >= 14 now works.
- XML: The value of the xml:lang attribute, inserted by msgfmt, is now
more correct.
There is a new runtime dependency:
* The Gnulib localizations.
+ Recommended.
Needed for localization of some of the programs to the user's language.
+ Documentation:
https://www.gnu.org/software/gnulib/manual/html_node/Localization.html
+ Download:
https://ftp.gnu.org/gnu/gnulib/gnulib-l10n-*
This is a new package, not yet contained in Guix.
New releases of some other packages (coreutils, diffutils, tar, etc.) will
depend on this package as well.
Pure localization packages have a precedent: The packages icecat-l10n,
icedove-l10n are similar.
According to [1], you are packaging gettext for Guix.
I invite you to upgrade to version 0.23.1.
Best regards,
Bruno
[1] https://git.savannah.gnu.org/cgit/guix.git/log/gnu/packages/gettext.scm
next reply other threads:[~2025-01-08 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 8:55 Ludovic Courtès [this message]
2025-01-08 17:58 ` [Bruno Haible] GNU gettext 0.23.1 is released Janneke Nieuwenhuizen
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tta9wuqj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=janneke@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).