I haven't looked at this filter myself... is the end result that rather than getting strings as input you get unicode objects (that are properly decoded UTF8?) Seems like a good default to me.
Can you open a ticket on this? We can certainly put this in for 0.9. http://trac.turbogears.org/ Kevin On 11/28/05, Jonathan LaCour <[EMAIL PROTECTED]> wrote: > > Is there any particular reason that the CherryPy decodeFilter isn't > enabled by *default* in TurboGears? This gave me fits earlier today, > and once I found the solution, I was puzzled why this isn't on by > default. Kid assumes UTF-8, and most browsers submit UTF-8, so it > seems like this should be on in the [global] section as follows: > > decodingFilter.on = True > decodingFilter.encoding = "utf8" > > Am I wrong? > > Jonathan LaCour > http://cleverdevil.org > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
