view ChangeLog @ 164:e1199c0fb3bf trunk

made the python extractor detect source file encodings from the magic encoding comment (or default to ascii) and convert message strings and comments to unicode fixes #23
author pjenvey
date Fri, 22 Jun 2007 00:38:54 +0000
parents 23005b4efc99
children 62b8e2a8caad
line wrap: on
line source
Version 0.9
http://svn.edgewall.org/repos/babel/tags/0.9.0/
(?, from branches/stable/0.9.x)

 * Added compilation of message catalogs to MO files.

Version 0.8.1
http://svn.edgewall.org/repos/babel/tags/0.8.1/
(?, 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.


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