view ChangeLog @ 222:7945923e5fa6

o extract_python fixes: - now returns None for non-string arguments - no longer extracts strings from nested function calls refs #38 - use the correct starting line number in multi-line gettext function calls - avoids falsely identifying string keyword arg defaults from function definition names that match a keyword, e.g.: def gettext(foo='bar') - avoid capturing translator comments embedded within a gettext function call - default the file encoding to iso-8859-1 instead of ascii when missing a magic encoding comment, to emulate pre Python 2.5 behavior. Python warns about 'non-ascii' chars when there is no magic encoding comment, but < 2.5 actually treats them as iso-8859-1 for backwards compat (PEP 263). >= 2.5 treats them as strict ascii o extract fixes: - filter out messages that don't contain strings where the keyword specification calls for fixes #39 - filter out empty string messages and emit a warning about them, like xgettext
author pjenvey
date Wed, 18 Jul 2007 00:29:04 +0000
parents 677147547e2d
children 3703ded648ab
line wrap: on
line source
Version 0.9
http://svn.edgewall.org/repos/babel/tags/0.9.0/
(?, from branches/stable/0.9.x)

 * The `new_catalog` distutils command has been renamed to `init_catalog` for
   consistency with the command-line frontend.
 * Added compilation of message catalogs to MO files (ticket #21).
 * Added updating of message catalogs from POT files (ticket #22).
 * Support for significant digits in number formatting.
 * Apply proper "banker's rounding" in number formatting in a cross-platform
   manner.
 * The number formatting functions now also work with numbers represented by
   Python `Decimal` objects (ticket #53).
 * Added extensible infrastructure for validating translation catalogs.
 * Fixed the extractor not filtering out messages that didn't validate against
   the keyword's specification (ticket #39).
 * Fixed the extractor raising an exception when encountering an empty string
   msgid. It now emits a warning to stderr.
 * Numerous Python message extractor fixes: it now handles nested function
   calls within a gettext function call correctly, uses the correct line number
   for multi-line function calls, and other small fixes (tickets #38 and #39).


Version 0.8.1
http://svn.edgewall.org/repos/babel/tags/0.8.1/
(Jul 2 2007, from branches/stable/0.8.x)

 * `default_locale()` would fail when the value of the `LANGUAGE` environment
   variable contained multiple language codes separated by colon, as is
   explicitly allowed by the GNU gettext tools. As the `default_locale()`
   function is called at the module level in some modules, this bug would
   completely break importing these modules on systems where `LANGUAGE` is set
   that way.
 * The character set specified in PO template files is now respected when
   creating new catalog files based on that template. This allows the use of
   characters outside the ASCII range in POT files (ticket #17).
 * The default ordering of messages in generated POT files, which is based on
   the order those messages are found when walking the source tree, is no
   longer subject to differences between platforms; directory and file names
   are now always sorted alphabetically.
 * The Python message extractor now respects the special encoding comment to be
   able to handle files containing non-ASCII characters (ticket #23).
 * Added 'N_' (gettext noop) to the extractor's default keywords.
 * Made locale string parsing more robust, and also take the script part into
   account (ticket #27).
 * Added a function to list all locales for which locale data is available.
 * Added a command-line option to the `pybabel` command which prints out all
   available locales (ticket #24).
 * The name of the command-line script has been changed from just `babel` to
   `pybabel` to avoid a conflict with the OpenBabel project (ticket #34).


Version 0.8
http://svn.edgewall.org/repos/babel/tags/0.8.0/
(Jun 20 2007, from branches/stable/0.8.x)

 * First public release
Copyright (C) 2012-2017 Edgewall Software