gettext-tools-windows

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

Upstream bugfixes release.

Bugfixes release.

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.

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.

Addresses a bug with UNC paths.

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.

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.

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.

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.

Notable changes in this release:

• Support for reproducible builds:
  • msgfmt now produces little-endian .mo files by default.
• Programming languages support:
  • XML:
    xgettext and msgfmt now look for .its files in directories supplied through the GETTEXTDATADIRS or XDG_DATA_DIRS environment variable.
  • JavaScript:
    xgettext and msgfmt now recognize numbered arguments in format strings.

See also upstream announcement.

Changes specific to gettext-tools-windows build:

• Fixed broken relocation support and unified files organization between ZIP and NuGet versions.
• Added ability to override output console encoding with GETTEXTIOENCODING variable.
• Gettext tools are built with localization support enabled now.

Upstream changes:

• Programming languages support:
  • XML: xgettext can now load custom string extraction rules supplied by consumer projects. The rules are written in XML, conforming the Internationalization Tag Set (ITS) standard. All the existing XML-based language scanners (Glade, GSettings, and AppData) are rewritten using ITS. In addition, msgfmt now has --xml option to merge translations back to the original XML document.
• Portability:
  • Improve OS/2 kLIBC support (still not complete)
  • Remove dependency on expat

See also upstream announcement.

• Programming languages support:
  • AppData: xgettext now supports AppData file format, used by software center applications (e.g., GNOME Software) to describe installable applications.
• A new macro AM_GNU_GETTEXT_REQUIRE_VERSION can be used to indicate autopoint to pull the latest available infrastructure, instead of the exact version specified with AM_GNU_GETTEXT_VERSION. When AM_GNU_GETTEXT_REQUIRE_VERSION is used, AM_GNU_GETTEXT_VERSION is ignored.
• po/Makefile.in.in can now insert the file $(DOMAIN).pot-header to $(DOMAIN).pot, instead of the standard header comments.
• Bug fixes:
  • Fix mishandling of gettext version numbers for minor releases, in po-mode.el and gettextize.
  • Fix build with --enable-relocatable.

See also upstream announcement.

• xgettext now has a feature to perform syntax checks on msgid, which could enforce common styles of translatable strings, such as to prefer Unicode characters to the corresponding ASCII characters. They can be enabled with --check option or special "xgettext: " comment in the source code. By default, no syntax checks are enabled.
• msgfilter and msgexec now have an option --newline, which appends a newline character to filter input and trims it from the filter output. This would allow filter programs to be more POSIX friendly.
• The base Unicode standard is now updated to 8.0.0. This particularly improves "\N{...}" notation handling of xgettext for Perl and Python.
• msginit is now capable of generating "Plural-Forms:" from Unicode CLDR. This feature is still experimental, but you can try it by setting the GETTEXTCLDRDIR environment variable pointing to the the directory where the CLDR archive is extracted. The actual conversion is done by a helper program 'cldr-plural', which can be used as a generic converter and evaluator of CLDR plural forms.
• Programming languages support:
  • C++ with KDE: xgettext and msgfmt can now recognize KUIT (KDE User Interface Text) markup. See the documentation section "KUIT Format Strings" for more info.
  • C++ with KDE: xgettext now recognizes all default KDE keywords. This removes the need for a long list of --keyword and --flag options to perform a reasonable extraction.
• Bug fixes:
  • xgettext C++11 raw string recognition is now stricter and don't accept unbalanced delimiters.
  • Suppress baseless warnings which msgfmt emits when processing a .desktop file.
  • xgettext line wrapping behaviour is now consistent between comment lines and non-comment lines.
  • Fix msgfilter-7 test failure on some platforms.
  • Fix VPATH build.

See also upstream announcement for 0.19.5 and 0.19.5.1.

• The --keyword option of xgettext now accepts same argument number for both singular and plural forms.
• Programming languages support:
  • C#: xgettext now properly handles Unicode characters encoded with
    surrogate pairs.
  • C/C++: xgettext now recognizes ISO/IEC 9899:2011 string literals
    prefixed by R, u8, u8R, u, uR, U, UR, L, or LR.
  • Shell: xgettext now properly recognizes Bash ANSI-C quoting ($'...').
• Bug fixes:
  • Fix integer overflow when reading certain MO files with msgunfmt.
  • Avoid invalid memory access in various cases. In particular, when
    the same argument number is specified for singular/plural
    arguments, and when checking Lisp and Scheme format strings.

See upstream announcement for more details.

• Fix xgettext mishandling of octal character escapes in C.
• Fix autopoint infinite recursion with certain configure.ac.

See upstream announcement for more details.

Fixes invalid memory access in xgettext when parsing empty string literals in C/Vala.

See upstream announcement for more details.

Fixes for issues with 0.19.

See upstream announcement for more details.

• New support for .desktop and GSettings files.
• Improved JavaScript, PHP, Python, Scheme, C and Vala support.
• Misc tools improvements.

See upstream announcement for more details.

• Apply PHP heredoc parsing patch.
• Rebuild binaries with secure features (NX, DYNAMICBASE, SAFESEH) enabled.