Permalink
Browse files

[e] (0) use more consistent wording (this is referred to as migration…

… in other parts of the spec)

git-svn-id: http://svn.whatwg.org/webapps@4928 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
Hixie committed Mar 31, 2010
1 parent 4ddefeb commit 88e06d6792c3de1f9ba8b7e65c1620c494db373f
Showing with 30 additions and 27 deletions.
  1. +10 −9 complete.html
  2. +10 −9 index
  3. +10 −9 source
View
@@ -2355,17 +2355,18 @@ <h4 id=restrictions-on-content-models-and-on-attribute-values><span class=secno>
</dd>
<dt>Errors that are intended to help authors of polyglot documents</dt>
<dt>Errors that are intended to help authors migrating to and from XHTML</dt>
<dd>
<p>Some authors like to write files that can be interpreted as
both XML and HTML with similar results. These are known as
polyglot documents. Though this practice is discouraged in general
due to the myriad of subtle complications involved (especially
when involving scripting, styling, or any kind of automated
serialization), this specification has a few restrictions intended
to at least somewhat mitigate the difficulties.</p>
both XML and HTML with similar results. Though this practice is
discouraged in general due to the myriad of subtle complications
involved (especially when involving scripting, styling, or any
kind of automated serialization), this specification has a few
restrictions intended to at least somewhat mitigate the
difficulties. This makes it easier for authors to use this as a
transitionary step when migrating between HTML and XHTML.</p>
<p class=example>For example, there are somewhat complicated
rules surrounding the <code title=attr-lang><a href=#attr-lang>lang</a></code> and
@@ -2375,8 +2376,8 @@ <h4 id=restrictions-on-content-models-and-on-attribute-values><span class=secno>
<p class=example>Another example would be the restrictions on
the values of <code title="">xmlns</code> attributes in the HTML
serialization, which are intended to ensure that elements in
conforming polyglot documents end up in the same namespaces
whether processed as HTML or XML.</p>
conforming documents end up in the same namespaces whether
processed as HTML or XML.</p>
</dd>
View
19 index
@@ -2253,17 +2253,18 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
</dd>
<dt>Errors that are intended to help authors of polyglot documents</dt>
<dt>Errors that are intended to help authors migrating to and from XHTML</dt>
<dd>
<p>Some authors like to write files that can be interpreted as
both XML and HTML with similar results. These are known as
polyglot documents. Though this practice is discouraged in general
due to the myriad of subtle complications involved (especially
when involving scripting, styling, or any kind of automated
serialization), this specification has a few restrictions intended
to at least somewhat mitigate the difficulties.</p>
both XML and HTML with similar results. Though this practice is
discouraged in general due to the myriad of subtle complications
involved (especially when involving scripting, styling, or any
kind of automated serialization), this specification has a few
restrictions intended to at least somewhat mitigate the
difficulties. This makes it easier for authors to use this as a
transitionary step when migrating between HTML and XHTML.</p>
<p class=example>For example, there are somewhat complicated
rules surrounding the <code title=attr-lang><a href=#attr-lang>lang</a></code> and
@@ -2273,8 +2274,8 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<p class=example>Another example would be the restrictions on
the values of <code title="">xmlns</code> attributes in the HTML
serialization, which are intended to ensure that elements in
conforming polyglot documents end up in the same namespaces
whether processed as HTML or XML.</p>
conforming documents end up in the same namespaces whether
processed as HTML or XML.</p>
</dd>
View
19 source
@@ -1195,17 +1195,18 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
</dd>
<dt>Errors that are intended to help authors of polyglot documents</dt>
<dt>Errors that are intended to help authors migrating to and from XHTML</dt>
<dd>
<p>Some authors like to write files that can be interpreted as
both XML and HTML with similar results. These are known as
polyglot documents. Though this practice is discouraged in general
due to the myriad of subtle complications involved (especially
when involving scripting, styling, or any kind of automated
serialization), this specification has a few restrictions intended
to at least somewhat mitigate the difficulties.</p>
both XML and HTML with similar results. Though this practice is
discouraged in general due to the myriad of subtle complications
involved (especially when involving scripting, styling, or any
kind of automated serialization), this specification has a few
restrictions intended to at least somewhat mitigate the
difficulties. This makes it easier for authors to use this as a
transitionary step when migrating between HTML and XHTML.</p>
<p class="example">For example, there are somewhat complicated
rules surrounding the <code title="attr-lang">lang</code> and
@@ -1215,8 +1216,8 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<p class="example">Another example would be the restrictions on
the values of <code title="">xmlns</code> attributes in the HTML
serialization, which are intended to ensure that elements in
conforming polyglot documents end up in the same namespaces
whether processed as HTML or XML.</p>
conforming documents end up in the same namespaces whether
processed as HTML or XML.</p>
</dd>

0 comments on commit 88e06d6

Please sign in to comment.