Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2003-April/034685.html below:

[I18n-sig] Changes to gettext.py for Python 2.3

• Previous message: [Python-Dev] Re: [I18n-sig] Changes to gettext.py for Python 2.3
• Next message: [Python-Dev] Re: More int/long integration issues
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sat, 2003-04-12 at 06:34, Martin v. Löwis wrote:
> Barry Warsaw <barry@python.org> writes:
> 
> > I suppose we could cache the conversion to make the next lookup more
> > efficient.  Alternatively, if we always convert internally to Unicode we
> > could encode on .gettext().  Then we could just pick One Way and do away
> > with the coerce flag.
> 
> If you are concerned about efficiency, I guess there is no way to
> avoid converting the file to Unicode on loading. I would then
> encourage a change where this flag is available, but has an effect
> only on performance, not on the behaviour.
> 
> Alternatively, you could subclass GNUTranslation.

It would take some refactoring, unless you implemented a second pass
over the catalog.  I'd rather not do either, so I'm happy to include
this right in GNUTranslations.

-Barry

• Previous message: [Python-Dev] Re: [I18n-sig] Changes to gettext.py for Python 2.3
• Next message: [Python-Dev] Re: More int/long integration issues
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4