> Well, If we send the page as ISO-8859-1 the user will send us data
> encoded as ISO-8859-1, and everything will be fine. We decode the POST
> data using the same encoding we will send that page in. I'm not sure what
> will happen if the user tries to POST non-ISO-8859-1 characters, though.
Zope3 can only decode if this is a POST request. Our search forms use GET
(to make them bookmarkable) - I suspect this data is assumed to be UTF-8.
> Anyway, I agree that we should ignore the header and always send UTF-8.
> I think that will cause us and the users the least amount of problems.
Björn Tillenius wrote:
> Well, If we send the page as ISO-8859-1 the user will send us data
> encoded as ISO-8859-1, and everything will be fine. We decode the POST
> data using the same encoding we will send that page in. I'm not sure what
> will happen if the user tries to POST non-ISO-8859-1 characters, though.
Zope3 can only decode if this is a POST request. Our search forms use GET
(to make them bookmarkable) - I suspect this data is assumed to be UTF-8.
> Anyway, I agree that we should ignore the header and always send UTF-8.
> I think that will cause us and the users the least amount of problems.
-- www.canonical. com/ www.ubuntu. com/
Stuart Bishop <email address hidden> http://
Canonical Ltd. http://