W3C home > Mailing lists > Public > www-tag@w3.org > January 2013

Re: NUís polyglot possibilities (Was: The non-polyglot elephant in the room)

From: Karl Dubost <karl@la-grange.net>
Date: Fri, 25 Jan 2013 11:08:43 -0500
Message-Id: <C759FD0C-7AA2-49AE-9977-6D8FF7AC7E82@la-grange.net>
Cc: public-html WG <public-html@w3.org>, "www-tag@w3.org List" <www-tag@w3.org>
To: Alex Russell <slightlyoff@google.com>

Le 24 janv. 2013 ŗ 17:14, Alex Russell a ťcrit :
> who benefits from the creation of polyglot documents?

I'm not sure I have the answer, but let's share a personal use case. To be honest I'm not sure it is entirely in the polyglot paradigm, but first of all:

> I don't understand why that ecosystem doesn't protect its borders by transforming HTML documents (via an HTML parser->DOM->XML serialization) to XML.

complexity and knowledge/habits with regards to one techno.

Now for my own use case (not mainstream, very specific and honestly, it's working for me as it is without really being polyglot).

In the spirit of bake not fried, I serve static files. The Web site is managed off the grid with scripts on my local computer. All the files are in "HTML5 with a king of xhtml syntax" no empty elements, double quotes. This allows me two very simple things:

* a poor man well-formed check in the browser when I'm editing the document. (application/xhtml+xml)
* a possibility to use an xml toolchain to parse the document and produces a few things such as a feed, etc.

then when the document is synced online, I can just serve it as text/html

As I said, not a point on promoting polyglot, just an explanation (triggered by your comment) on why some people may use both content-types at the level of the document itself.

/me is returning to the evasnescence of internet limbos. 

Karl Dubost, a Web opener to hire
Received on Friday, 25 January 2013 16:08:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:51 UTC