Am 25.07.2011 21:31 schrieb Alessandro Molina:
Otherwise there might be cases where the controller reports a content-type and the meta tag another one if the users switched content type from the controller without making the template content type dependent from a variable.
Actually if you're using templates you can't switch the content type (charset) in the controller anyway since you would need to also switch the output encoding of the templating engine which TG2 does not support.
Any issue that I'm unable to see?
One reason for keeping the meta tags is that they are useful when you store or cache pages for offline reading. Otherwsie, the content-type sent in the http header always takes precedence, so they will not harm even if they are wrong.
Btw, this was one of the things I liked in Kid templates, where the engine injected the right meta tag in its output automatically.
-- Christoph -- 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.
