Hi
Malcolm Tredinnick wrote:
> What I don't think is the right answer is to suddenly start making
> gettext() behave as if it were ugettext() -- using the wrong name for
> something will lead to confusion for people who use Django as a tool,
> not as a lifestyle choice.
Certainly. Think about the other case: A developer who is still using
utf8 encoded bytestrings would use
gettext('blablabla %s blablalba') % \
"utf8 bytestring with funny รครค chars"
If gettext returned unicode, python would decode the utf8 encoded
bytestring, again using ASCII as default encoding -> exception galore ;-)
And what function should be used for the usual _()?
Unfortunately, I don't have a nice solution to this at hand, either.
Michael
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
