"Kevin Dangoor" <[EMAIL PROTECTED]> writes: > The encoding that it's set to use is utf-8. Do people have browsers > out there that would be sending data encoded in something other than > utf-8?
IIRC, the encoding used to send data should be the same that is used to receive data. So, if someone configures it's code to use, e.g., iso-8859-1 then the browser will be expecting iso-8859-1 data and will be sending iso-8859-1 as well. The same might happen for more esoteric encodings such as the ones used by Windows (cp*). > This value is still changeable in the config file. It just seemed that > the current default of not decoding the input is not a desirable > default. Agreed. I'd go a step further and configure it to use the same value as kid.encoding = "utf-8" in app.cfg. This ties the configuration and makes it consistent between TG and Kid. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
