#14801: Support for string methods with lazy translations
-------------------------------------------+--------------------------------
Reporter: bronger | Owner: nobody
Status: closed | Milestone:
Component: Internationalization | Version: 1.2
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => wontfix
Comment:
I might be missing something here, but doesn't seem like something that is
in Django's court. Django just uses GNU gettext for translations. There's
a bunch of wrappers around the outside to enable and disable various
translation contexts, but the core translation calls (gettext / _()) are
proxied directly to gettext. lower/upper etc aren't features exposed by
gettext, so they're not features exposed by Django, either.
There's also the issue of what "Upper" means; in a raw python string,
"foo".upper() -> "FOO", not "Foo". "foo".capitalize() -> "Foo" but full
capitalization rules are locale specific, and aren't even implemented
consistently for English.
Marking wontfix, since this appears to be somewhere between an intractable
problem and a problem that isn't Django's domain.
--
Ticket URL: <http://code.djangoproject.com/ticket/14801#comment:3>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
