On Mon, 2009-01-26 at 10:35 -0800, Ty wrote: > Thanks for the link. > I'm supprised there nothing "built-in" to allow this. Django's > essentally pushing you to use XHTML over HTML. > > Not really a big deal though, I suppose.
Precisely. In XHTML, validity errors must be handled by not parsing the remainder of the page, and hence, not rendering (XML's required error handling technique). In HTML, the requirement for errors of this form (<input /> instead of <input >), is that the parser *must* recover in a way that forces it to treat it as "<input >" -- it has to ignore the invalid characters and recover in a particular, well-defined fashion. That's a requirement of the SGML specification (on which HTML is based). So HTML parsers interpret what Django produces correctly, even though it isn't strictly valid. That's why non-validity for HTML, when it's this kind of non-validity isn't a really big deal. It's cosmetic, rather than tragic. It's also why the django-html project exists and why, maybe, one day, such an option will exist in Django. But the right API and how much parallel maintenance it will require is, as yet, highly unclear. So an external project or two experimenting with the possibilities is absolutely the right way to go about things. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
