hi,
i think it would be a good idea, to define what the "unicode policy" of
newforms should be.
i got the idea after seeing changeset 4076....
i understand that this is still work-in-progress, but we still should
clearly define how we handle incoming data.
so, some question:
- what is the plan, how should incoming data (GET or POST) handled?
some possibilities:
- we assume it's DEFAULT_CHARSET. we do not failover (means that if that
data is not in DEFAULT_CHARSET, the newforms code will (because of
"unicode(data,DEFAULT_CHARSET) raise the usual UnicodeDecodeError)
or
- we will make sure that we never raise such an error. that would mean,
that, for example:
- we try DEFAULT_CHARSET
- if we fail, we try <something_else_1> (probably utf-8)
- if we fail, we try <something_else_2>
.
.
.
- if we fail, we use ISO-8859-1 (which cannot fail)
so, which direction should be taken?
gabor
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" 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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
