#3063: [patch] i18n broken for msgids with extended characters
------------------------+---------------------------------------------------
Reporter: akaihola | Owner: hugo
Status: new | Component: Internationalization
Version: | Resolution:
Keywords: i18n | Stage: Design decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------+---------------------------------------------------
Changes (by mtredinnick):
* stage: Accepted => Design decision needed
Comment:
This is a really expensive change, performance-wise: every string now
passes through a call to encode() prior to display. Since the alternative
is do a more or less once-off translation of the source templates to
UTF-8, I'm not convinced the performance hit is justified. I'm normally a
big advocate for supporting more than just UTF-8 encodings because of the
benefits to East Asian locales, but in this case even I'm not sure. Moving
back to "design decision needed" for a bit more thinking.
--
Ticket URL: <http://code.djangoproject.com/ticket/3063#comment:4>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
