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.