Am 26.07.2011 01:18, schrieb Alessandro Molina:
> Next step might be to have the quickstart template that sets the meta
> tag using response.content_type.
Yes, this should work. We could include the charset here as well:
<meta http-equiv="content-type"
content="${response.content_type}; charset=${response.charset}"/>
Btw, we have a similar problem with the doctype. As far as I see, in TG2
you cannot change it or have it automatically adapt to the content type
(e.g. HTML, XMTML1, HTML5).
In TG1+Kid it was possible to switch the output encoding or method from
XHTML to HTML output by changing one config setting only, everything was
serialized properly according to the method, and doctype and meta tags
were injected as necessary. The templates would always be XHTML, but the
output was flexible. But maybe this feature is not so interesting any
more since XHTML is dead and it would be difficult to realize with
non-XML templating engines like Mako or Jinja.
Also, should we start creating HTML5 templates on quickstart?
-- 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.
