On 8 Jan., 06:21, Sam <[email protected]> wrote: > I added > tools.encode.encoding = "utf-8" > to the global section of my app.cfg and success!
As far as I understand, the problem seems to be that CP 3.2 has tools.encode on by default, and tries to encode to the first accepted charset. This is often iso-8859-1 instead of utf-8, but TG returns the response already encoded as utf-8, not as unicode, so this does not work and the utf-8 output will be declared as iso-8859-1 which renders garbage. So I think the better and more performant solution is to completely switch off the encode tool because it's not needed. Can you check how that works for you? I.e. instead of tools.encode.encoding = "utf-8" set: tools.encode.on = False -- Christoph -- 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?hl=en.
