- From: CVS User egraff <cvsmail@w3.org>
- Date: Mon, 03 Feb 2014 22:35:57 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/html-polyglot
In directory roscoe:/tmp/cvs-serv19350
Modified Files:
html-polyglot.html
Log Message:
Correct date of the draft
--- /sources/public/html5/html-polyglot/html-polyglot.html 2014/02/03 22:35:14 1.27
+++ /sources/public/html5/html-polyglot/html-polyglot.html 2014/02/03 22:35:57 1.28
@@ -8,7 +8,7 @@
var respecConfig = {
specStatus: "ED",
shortName: "html-polyglot",
- publishDate: "2014-02-01",
+ publishDate: "2014-02-03",
previousPublishDate: "2010-10-19",
// previousDiffURI: "http://htmlwg.org/heartbeat/WD-html-polyglot-20131008/",
previousMaturity: "WD",
@@ -359,8 +359,8 @@
omitting a tag in <a>polyglot markup</a> is equivalent to producing a document that is not well-formed or,
if both tags are omitted, equivalent to not adding the element at all. </p>
- <p>That <a>polyglot markup</a> doesn’t operate with optional tags, may create surprises for an author not used
- to adding the <code>tbody</code> tags in their code, for example,
+ <p>The fact that <a>polyglot markup</a> doesn’t operate with optional tags may create surprises for an author not used
+ to adding the <code>tbody</code> tags in their markup, for example,
or to someone accustomed to omitting the end tag of the <code>p</code> element.
However, the requirement to be well-formed with regard to tags is a key feature of <a>polyglot markup</a>
that makes the code <a href="#dfn-robust-syntax">robust</a> against subpar parsers and authoring surprises.
Received on Monday, 3 February 2014 22:35:58 UTC