#3600: Newforms label translation fails
---------------------------------------------------------+------------------
Reporter: Timo |
Owner: adrian
Status: new |
Component: django.newforms
Version: SVN |
Resolution:
Keywords: newforms translation internationalization |
Stage: Accepted
Has_patch: 1 |
Needs_docs: 0
Needs_tests: 0 |
Needs_better_patch: 1
---------------------------------------------------------+------------------
Changes (by mtredinnick):
* needs_better_patch: 0 => 1
* stage: Ready for checkin => Accepted
Comment:
I'm not happy with this patch. It fixes the symptom, but not the cause of
the problem. We want to be turning things into unicode as early as
possible, so doing it in the Field class is the right thing. Moving the
unicode conversion until later is inconsistent and leaves us with multiple
encodings floating around internally -- something we are trying to slowly
get rid of. A better fix is to work out why we aren't then translating
that unicode value, which is, I suspect a deeper problem.
This is a genuine bug and the test case is good to have, but it isn't the
right fix. I want to dig a bit deeper into this before committing
anything.
--
Ticket URL: <http://code.djangoproject.com/ticket/3600#comment:6>
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
-~----------~----~----~----~------~----~------~--~---
