delta/cpython.git/Lib/gettext.py, branch v2.7

close file explicitly

2009-05-10T01:38:02+00:00

Patch #1349274: gettext.install() now optionally installs additional

2006-02-19T13:26:36+00:00

translation functions other than _() in the builtin namespace.

Use cStringIO where available.

2004-12-31T19:15:26+00:00

This change implements the following gettext features, as

2004-07-22T18:44:01+00:00

discussed recently in python-dev:

In _locale module:

- bind_textdomain_codeset() binding

In gettext module:

- bind_textdomain_codeset() function
- lgettext(), lngettext(), ldgettext(), ldngettext(),
  which return translated strings encoded in
  preferred system encoding, if
  bind_textdomain_codeset() was not used.
- Added equivalent functionality in translate()
  function and catalog classes.

Every change was also documented.

Replace str.find()!=1 with the more readable "in" operator.

2004-05-04T09:21:43+00:00

GNUTranslations._parse(): Initialize local variable k so that if the

2003-10-04T02:28:31+00:00

first line of a header section isn't an RFC-ish header, it's just
ignored instead of throwing an UnboundLocalError.

Backport candidate.

GNUTranslations._parse(): Fix SF bug #658233, where continuation lines

2003-05-20T17:26:48+00:00

in .po metadata caused a crash.

Backport candidate.

GNUTranslations:

2003-04-24T18:13:39+00:00

    __init__(): Removed since we no longer need the coerce flag.
    Message ids and strings are now always coerced to Unicode, /if/
    the catalog specified a charset parameter.

    gettext(), ngettext(): Since the message strings are Unicodes in
    the catalog, coerce back to encoded 8-bit strings on return.

    ugettext(), ungettext(): Coerce the message ids to Unicode when
    there's no entry for the id in the catalog.

Minor code cleanups; use booleans where appropriate.

NullTranslations.init(): Back out of setting the default charset

2003-04-11T20:26:47+00:00

to iso-8859-1.

GNUTranslations._parse(): Back out the addition of a test for
Project-ID-Version in the metadata.  This was deliberately removed in
response to SF patch #700839.

Also, re-organize the code in _parse() so we parse the metadata header
containing the charset parameter before we try to decode any strings
using charset.

From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html

2003-04-11T18:36:43+00:00

- Expose NullTranslations and GNUTranslations to __all__

- Set the default charset to iso-8859-1.  It used to be None, which
would cause problems with .ugettext() if the file had no charset
parameter.  Arguably, the po/mo file would be broken, but I still think
iso-8859-1 is a reasonable default.

- Add a "coerce" default argument to GNUTranslations's constructor.  The
reason for this is that in Zope, we want all msgids and msgstrs to be
Unicode.  For the latter, we could use .ugettext() but there isn't
currently a mechanism for Unicode-ifying msgids.

The plan then is that the charset parameter specifies the encoding for
both the msgids and msgstrs, and both are decoded to Unicode when read.
For example, we might encode po files with utf-8. I think the GNU
gettext tools don't care.

Since this could potentially break code [*] that wants to use the
encoded interface .gettext(), the constructor flag is added, defaulting
to False.  Most code I suspect will want to set this to True and use
.ugettext().

- A few other minor changes from the Zope project, including asserting
that a zero-length msgid must have a Project-ID-Version header for it to
be counted as the metadata record.