gettext-0.12-pre1 available for testing
Bruno Haible <[email protected]> Wed, 19 Feb 2003 22:22:25 +0100 (CET)
| Newsgroups | gmane.comp.sysutils.autotools.announce |
|---|---|
| Message-ID | <[email protected]> |
Hi, Six months after 0.11.5, the first prerelease of gettext-0.12. http://www.haible.de/bruno/gnu/gettext-0.12-pre1.tar.gz This is a test release of GNU gettext. Please do not send reports about this release to any GNU mailing list or newsgroup. Please send comments and problems to <bruno at clisp.org>. Note that test release numbers cannot be given as argument to the "autopoint" program. Therefore please don't use the "gettextize" program of this test release on projects which you share with other programmers via CVS. News: * The gettext package is now separated into two subpackages: - gettext-runtime: Runtime libraries and programs. - gettext-tools: Tools and documentation for developers and translators. The 'gettext-runtime' package is very small and should be installed on every system that has users who desire to use internationalization. Whereas the 'gettext-tools' package is only for developers and translators. * The po/Makevars file has a new field MSGID_BUGS_ADDRESS, which program maintainers should fill in, to help feedback from the translators to the program maintainers. xgettext, accordingly, has a new option --msgid-bugs-address. * xgettext now also supports Smalltalk and PHP. * A new C++ class, called gnu::autosprintf, makes it possible to use C format strings in C++. This is needed for proper internationalization of C++ programs. * A new include file libgettextpo, with public header file "gettext-po.h", provides functions for reading PO files into memory. It is useful for applying PO files to areas not covered by the GNU gettext programs. New documentation section: - Writing your own programs that process PO files. * New documentation section: - Prioritizing messages: How to determine which messages to translate first. * xgettext now supports msgid strings in other encodings than ASCII. xgettext has a new option --from-code that specifies the encoding of the source files. The resulting POT files are UTF-8 encoded. * msgmerge has a new option -N/--no-fuzzy-matching that inhibits the fuzzy search for untranslated messages. * msgattrib has new options --only-file and --ignore-file that cause the specified attribute manipulation to apply to selected messages only. * Compatibility with automake-1.7. * In documentation section po/LINGUAS: - Document the optional "languages" en@quot and en@boldquot.