Version 0.23

See upstream announcement.

Version 0.22.5

Upstream bugfixes release.

Version 0.22.4

⚠️ Starting with this version, the binaries are built as 64-bit and require UCRT.

Upstream bugfixes release.

Version 0.22.3

Bugfixes release.

Version 0.22

Notable changes in this release:

PO file format:

• When a #: line contains references to file names that contain spaces, these file names are surrounded by Unicode characters U+2068 and U+2069. This makes it possible to parse such references correctly.

Improvements for maintainers:

• The AM_GNU_GETTEXT macro now defines two variables localedir_c and localedir_c_make, that can be used in C code or in Makefiles, respectively, for representing the value of the --localedir configure option.

Programming languages support:

• C, C++:

  • xgettext now supports gettext-like functions that take wide strings (of type 'const wchar_t *', 'const char16_t *', or 'const char32_t *') as arguments.
  • xgettext now recognizes numbers with digit separators, as defined by ISO C 23, as tokens.
  • xgettext and msgfmt now recognize the format string directive %b (for binary integer output, as defined by ISO C 23) in format strings.
  • xgettext and msgfmt now recognize the argument size specifiers w8, w16, w32, w64, wf8, wf16, wf32, wf64 (as defined by ISO C 23) in format strings.
  • xgettext and msgfmt now recognize C++ format strings, as defined by ISO C++ 20. They are marked as 'c++-format' in POT and PO files. A new example has been added, 'hello-c++20', that illustrates how to use these format strings with gettext.

• Java:

  • The build system and tools now also support Java versions newer than Java 11. This is known to work up to Java 20, at least. On the other hand, support for old versions of Java (Java 1.5 and GCJ) has been dropped.

• Tcl: xgettext now supports the \x, \u, and \U escapes as defined in Tcl 8.6.

xgettext:

• The xgettext option --sorted-output is now deprecated.
• xgettext input files of type PO that are not all ASCII and not UTF-8 encoded are now handled correctly.

The base Unicode standard is now updated to 15.0.0.

See also upstream announcement.

The GETTEXTIOENCODING patch was removed.

Version 0.21.1

See upstream announcement.

⚠️ Deprecation notice:
The patch that adds the GETTEXTIOENCODING environment variable is now deprecated. Use gettext's standard OUTPUT_CHARSET instead as recommended by upstream.

Version 0.21-1

Addresses a bug with UNC paths.

Version 0.21

Notable changes in this release:

Programming languages support:

• Shell:
  • xgettext now recognizes and ignores env invocations and environment variable assignments in front of commands.
• Java:
  • xgettext now recognizes format strings in the Formatter syntax. They are marked as java-printf-format in POT and PO files.
  • xgettext now recognizes text blocks as string literals.
• JavaScript:
  • xgettext parses JSX expressions more reliably.
• Ruby:
  • xgettext now supports Ruby.
  • msgfmt -c now verifies the syntax of translations of Ruby format strings.

Runtime behaviour:

• On native Windows platforms, the directory that contains the message catalogs may now contain arbitrary Unicode characters. To make use of this feature, use the new function wbindtextdomain instead of bindtextdomain. It allows to pass a directory name in wchar_t[] encoding. Note: wbindtextdomain exists only on native Windows platforms.

Improvements for translators:

• When msgfmt writes a MO file, it now does so in such a way that processes that are currently using an older copy of the MO file will not crash.

Libtextstyle:

• Added support for emitting hyperlinks.
• New API for doing formatted output.
• The example programs support the NO_COLOR environment variable.

See also upstream announcement.

⚠️ Deprecation notice:
The patch that adds the GETTEXTIOENCODING environment variable is now deprecated. Use gettext's standard OUTPUT_CHARSET instead as recommended by upstream.

Version 0.20.2

Upstream release notes for 0.20.2

⚠️ Deprecation notice:
The patch that adds the GETTEXTIOENCODING environment variable is now deprecated. Use gettext's standard OUTPUT_CHARSET instead as recommended by upstream.

Version 0.20.1-1

Applied fix for JS template literals parsing.

Upstream release notes for 0.20 and for 0.20.1.

⚠️ Deprecation notice:
The patch that adds the GETTEXTIOENCODING environment variable is now deprecated. Use gettext's standard OUTPUT_CHARSET instead as recommended by upstream.