Den 17. aug. 2018 12:07, skrev James Bennett: > > XHTML5 itself is neither well-specified nor robust; the new elements > of HTML5 are more or less dumped by fiat into the old 1999/XHTML > namespace, but who's to say parsers will actually be aware of that? > Especially validating parsers? Can you point to a standardized XML > DTD, XSD, RELAX NG or, well, anything that's broadly accepted as > defining XHTML5? W3C doesn't publish one that I'm aware of, and the > Editor's Draft for Polyglot does not provide guidance. > > And speaking of validating parsers: HTML5 has a large set of named > entities. Validating XML parsers are required, as always, to accept > only the base five of XML, and can fatal-error on anything else. For > non-validating parsers, or for those which choose to accept more than > the base five named entities, XHTML and HTML historically did not > agree on the set (XHTML defined 253 named entities, HTML historically > defined at most 252). More fun times there. XML-ENTITY-NAMES tried to > alleviate this by defining and exposing entity sets documents could > refer to, but see again: validating parsers don't have to accept them. > Are we forbidden ever to use an HTML5 entity, or anything outside the > base five XML entities, in Django, in order to make sure serving > Django as XHTML works? I hope not.
I am talking about being able to serve pages as application/xhtml+xml, this is defined by browser support as is the SGML version of HTML5. I hardly think XML version of HML5 is more ill-defined than the SGML version. I am not talking about supporting validators, as the browsers are the validators. No need to use a validator if the browser makes it clear when it is not. No need to limit what entities to use as long at it is supported by the browsers. As for Javascript and the difference between a XML-dom and and HTML-dom. I have not run into this. I use Javascript to manipulate the DOM, but not heavily. Do the browsers generate different DOM when using application/xhtml+xml to server the pages? That is an argument to serve Django Admin as 'text/html', and let other apps choose for themselves. In my case it is only the use '/>' and giving attributes a value that stands in the way. Regards -- Nils Fredrik Gjerull ----------------------------- "Ministry of Eternal Affairs" Computer Department ( Not an official title :) ) -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ab2142a2-c4bc-0112-5fec-9cf537fc8959%40gjerull.net. For more options, visit https://groups.google.com/d/optout.
