#3924: Caught an exception while rendering: 'ascii' codec can't decode byte 0xc3
in position 8: ordinal not in range(128)
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: hugo
Status: reopened | Component: Template system
Version: SVN | Resolution:
Keywords: | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------------+--------------------------------------
Comment (by Ciantic):
> Replying to [comment:14 mtredinnick]:
> The solution in the previous comment will fail for Forms that are
created at import time and then the locale() changes before they are used.
It forces the translation to occur at the time smart_unicode() is called,
rather than at the moment of output (when the locale will be set
correcty). Which means almost 100% failures for many internationalised
applications.
>
> I am working on fixing the FIXME in that code at the moment.
I debugged one of my problems and final conclusion was same as in FIXME...
One question though, what bug will you mark as fixed when it is ready?
Since I could really need patch for this. I have now ugly hacks of using
decode here and there, where ever gettext_lazy and smart_unicode is used,
which mostly is in BaseForm btw.
--
Ticket URL: <http://code.djangoproject.com/ticket/3924#comment:22>
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
-~----------~----~----~----~------~----~------~--~---
