[Python-Dev] Re: [I18n-sig] Changes to gettext.py for Python 2.3 (original) (raw)
Barry Warsaw barry@python.org
16 Apr 2003 12:53:53 -0400
- 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 ]