--
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 django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
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/eb10d68f-706f-4bc3-4ee3-c440723aa0b4%40gjerull.net.
For more options, visit https://groups.google.com/d/optout.
You didn't pose an exact question in your message, but I guess it's "Can Django officially support XHTML5?"
As it's a stricter subset of HTML5, it seems a valid idea. But at the same time, we need to be able to support it going forwards, with test coverage and knowledge that this is what we aim for on every PR that adds HTML. Also I doubt you'll find many third party packages support XHTML5 too.
You say there's more to be fixed that just reversing #29038. What else is there? Would you be willing to do all the work?
I am willing to do the work. It is not much that need to be done. Just some query-replace to change the generated HTML into valid XML.
--
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 django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
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/d0645f61-836c-c908-98a9-b99dec62d5f6%40gjerull.net.
I still would like a technical answer to why not support both standards?
And again XHTML5 is HTML5 with valid XML syntax. So valid XHTML5 is
valid HTML5, so there is no problem for a framework to provide HTML5 it
should just be done in the most compatible manner.
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.
--
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 django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
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/CAL13Cg9UEtSBEPnc0_OJWy4HHALSA-XOLhgKBnnF5Fq7%3Dr811Q%40mail.gmail.com.
On 23 Aug 2018, at 19:33, Nils Fredrik Gjerull <ni...@gjerull.net> wrote:How can we move forward on supporting XML serialization of HTML5 (XHTML5)?
When I created the pull-request I did not think it would be very
controversial. After all, the XML style of writing HTML has been used
for years. I guess many are not aware that HTML5 comes in two flavors
and it creates confusion.