W3C home > Mailing lists > Public > public-html-diffs@w3.org > February 2011

eliot: Removed extra Introduction section. Oops. </blush>

From: poot <cvsmail@w3.org>
Date: Fri, 11 Feb 2011 20:04:31 -0500
To: public-html-diffs@w3.org
Message-Id: <E1Po3uZ-0007Zm-Ls@jay.w3.org>
eliot: Removed extra Introduction section. Oops. </blush>

http://dev.w3.org/cvsweb/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html?r1=1.55&r2=1.56&f=h

===================================================================
RCS file: /sources/public/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -d -r1.55 -r1.56
--- html-xhtml-authoring-guide.html	12 Feb 2011 00:32:21 -0000	1.55
+++ html-xhtml-authoring-guide.html	12 Feb 2011 01:03:19 -0000	1.56
@@ -206,30 +206,6 @@
 
 
 
-	<div id="introduction" class="section informative">
-		<h2><span class="secno">1. </span>Introduction</h2>
-		<p>
-			<em>This section is non-normative.</em>
-		</p>
-		<p>
-			It is often valuable to be able to serve HTML5 documents that are also well formed XML documents. 
-			An author may, for example, use XML tools to generate a document, and they and others may process the document using XML tools. 
-			These documents are served as text/html. 
-			The language used to create documents that can be parsed by both HTML and XML parsers is called <dfn id="dfn-polyglot-markup">polyglot markup</dfn>. 
-			<a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> is the overlap language of documents which are both HTML5 documents and XML documents. 
-		</p>
-		<p>
-			All web content need not be authored in <a>polyglot markup</a>.
-			<a title="polyglot markup">Polyglot markup</a> is ideal for publishing when there's a strong desire to serve both HMTL and XML tool chains 
-			without simultaneously having to maintain dual copies of the content: one in HTML and a second in XHTML. 
-			In addition, a single <a>polyglot markup</a> output requires less infrastructure to produce than to produce both HTML and XHTML output for the same content. 
-			<a title="polyglot markup">Polyglot markup</a> is also be beneficial when lightweight processes&#x2014;such as 
-			quick testing or even hand-authoring&#x2014;are applied to content intended to be published both as HTML and XHTML, 
-			especially if that content is not sent through a tool chain. 
-		</p>
-<!--End Section 1: Introduction-->
-	</div>
-
 <div id="PI-and-xml" class="section">
 <!--OddPage--><h2><span class="secno">2. </span>Processing Instructions and the XML Declaration</h2>
 <p>
Received on Saturday, 12 February 2011 01:04:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 12 February 2011 01:04:34 GMT