On 1/2/06, Max Ischenko <[EMAIL PROTECTED]> wrote: > I'm using Kid templates to serve dynamic pages and they produce HTML in > UTF-8 encoding. Turbogears processes and encodes them just fine but > CherryPy serves them as "text/html" (note the absence of the charset > field) which confuses browsers (e.g. Firefox 1.5 with auto-detect for > Russian turned on). > > Of course I can override this explicitly by passing content_type arg to > every expose() method but it feels a bit tedious. May be something more > intelligent can be developed? E.g.: if Kid template being served and > kid.encoding is set then derive server Content-Type from that. Or an > option to get the default charset from config file. > > What do you think? > > I was thinking about filing a ticket but I'm not sure what's the best > solution would be.
This is a good thought. Using the known encoding from kid.encoding is a good idea. Please open a ticket. Kevin
