One of the problems with maintaining translations is that they can easily
get out of date. Thus, Jeff's localization code will generate debug
warnings at runtime if you're using a stale translation, mentioning which
additional symbols need to be translated.
The other piece of the puzzle is getting an up-to-date English version to
translate. For this reason, debug versions of AbiWord support a
-dumpstrings command-line argument, which generates a new EnUS.strings file
based on the complete current set of builtin strings. The idea is that a
translator can take a copy of this file, rename and modify it accordingly,
and then submit it back to us.
Unfortunately, translators have been noticing that these auto-generated
EnUS.strings files were broken in two ways:
1. They didn't explicitly mention the required charset, so accented
characters frequently got garbled.
2. They included naked ampersand (&) characters for accelerator prefixes,
instead of the proper & entities.
All better now. :-)