2008/10/15 Christoph Zwerschke <[EMAIL PROTECTED]>: > > Christophe de VIENNE schrieb: >> Indeed, I wrote a decated templating engine that can generate, from a >> particular data structure, several kind of output. >> This made it possible to make the rendering engine choice handled by >> expose depending on the accept header (or tg_format). >> >> By the way, why is this charset not set for json ? > > This was answered here: > http://trac.turbogears.org/ticket/1995
Thanks, my curiosity is fully satisfied. > Btw, you can configure a default charset for your templating engine with > the setting "your_engine_name.encoding". If you set it to None, then no > charset will be added. But maybe your templating engine also produces > output where you want it added, then this won't help you. I don't really need nor want it to be added on any output in the context I use them. But it would definitely make sense to have it on some output I produce with this engine. > I think instead of using a blacklist for the mime types without charset > (currently only json) we should better use a whitelist for those mime > types where the charset should be added. > > Opinions? It seems a better option to me. In fact it was what I was expecting at first when reading the code. But that is only my 2 cents... I have no idea how many mime types may fall into this whitelist, or if it is a limited-length list. Christophe --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
