This is unrelated Andreas. HTML5 has the exact same syntax as HTML4, just new tags. This thread is about syntax.
By the way, neither html4 nor xhtml are deprecated. HTML5 is still not "officially released". J. Leclanche / Adys On Mon, Sep 28, 2009 at 12:12 PM, Andreas <andr...@klydd.se> wrote: > > html4 is derecated. > xhtml is deprecated. > > > With google chrome frame out there theres absolutly no reason to not > begin with html5 already. > The longer we wait, the longer it will take before html5 becomes "the > it". > > </rant> > > On Sep 27, 1:46 pm, Simon Willison <si...@simonwillison.net> wrote: >> On Sep 27, 10:49 am, veena <vsto...@gmail.com> wrote: >> >> > my bits to discussion about supporting various (X)HTML versions. >> >> > 1) Problem with (X)HTML in python code (in applications) >> > I discovered this python packagehttp://pypi.python.org/pypi/html/1.6 >> > It allows you to write "python like HTML syntax" and generates HTML or >> > XHTML. >> >> Something like that might be an option for cleaning up the way markup >> is generated within the forms framework itself, but ultimately I think >> adding an entirely new Python-based generation method just to output a >> few strings wouldn't be worth the added dependency. >> >> > 2) Problem with (X)HTML in templates >> > I think there should be parser, which parse template just before >> > caching templates. Code could be messy HTML or (XHTML) or invalid HTML >> > (like undisclosed tags, attributes without quotations marks etc.) and >> > from this make pretty HTML or XHTML according to html coder settings >> > by {% doctype %} >> >> The performance overhead rules out this kind of approach for Django >> core - any post-processing run against the output of the templates >> would be executed on every single Django request, and HTML parsing and >> rewriting is a very expensive operation. That's not to say a third >> party module couldn't be written to do this kind of thing for people >> who really want to clean up their output (I remember there being an >> HTMLTidy middleware a few years back that did this) but it wouldn't be >> suitable for inclusion in core. >> >> Cheers, >> >> Simon > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
