3c3
< <!-- $Author: lou $ $Author: lou $ $Date: 2001/09/21 $ $Id: //TEI/XMLodds/Odds/p2ab.odd#10 $ -->
---
> <!-- $Author: rahtz $ $Author: rahtz $ $Date: 2001/07/30 $ $Id: //TEI/XMLodds/Odds/p2ab.odd#9 $ -->
77c77
< is often called <soCalled>markup</soCalled>, <soCalled>encoding</soCalled>, or
---
> is often called <soCalled>markup</soCalled> or
130,132c130,131
< 
< <p>The rules and recommendations made in the these Guidelines are
< designed to enable the creation of documents that conform to either
---
> <p>The rules and recommendations made in the these Guidelines are designed to
> enable the creation of documents that conform to either 
137,151c136,146
< maximize compatibility with both specifications. For more information
< on markup languages see chapter <ptr target="SG" type="div1"/> .
< </p>
< 
< <p>These Guidelines also make reference to character encoding
< standards such as ISO 646 and Unicode. ISO
< 646 defines a standard seven-bit character set in terms of which
< recommendations on character-level interchange are formulated; this is
< the most portable character set for broad interchange, but requires
< indirect encoding of many characters.  Unicode provides a much larger
< character set appropriate for international use, and all XML
< implementations must support it; however, it is not as of this writing
< so widely portable as ISO 646.
< </p>
< 
---
> maximize compatibility with both specifications.</p>
> <p>These Guidelines also 
> make reference to ISO 646 and Unicode. ISO 646 defines a standard seven-bit
> character set in terms of which recommendations on character-level
> interchange are formulated; this is the most portable character set
> for broad interchange, but requires indirect encoding of many characters. 
> Unicode provides a much larger character set appropriate for international
> use, and all XML implementations must support it; however, it is not 
> as of this writing so widely portable as ISO646.
> For more information on markup languages see chapter <ptr target="SG" type="div1"/>
> .  </p>
184c179
< review of markup languages (chapter <ptr target="SG" type="div1"/>); and a description
---
> review of markup systems (chapter <ptr target="SG" type="div1"/>); and a description
238,239c233,234
< interchange format.  No formal subset has been defined for XML, since XML
< itself is a subset appropriate to these Guidelines.</p>
---
> interchange format (no formal subset has been defined for XML, since XML
> itself is a subset appropriate to these Guidelines).</p>
339c334
< exhibit the logical structure of the encoding more clearly.  Although
---
> exhibit the logical structure more clearly.  Although
359,360c354,355
< quotes. Unquoted attribute values are not permitted in XML, and so are
< not used except where otherwise noted, for example to emphasize a comparison
---
> quotes; unquoted attribute values are not permitted in XML, and so are
> not used except where otherwise noted (for example, to emphasize a comparison
463c458
< are constructed so that they can be easily converted to either language.
---
> are constructed so that they can be trivially converted to either language.
515c510
< made and often useful in narrow  well-defined contexts, are perhaps best
---
> made and often useful in narrow well defined contexts, are perhaps best
542c537
< features, but sometimes provide several alternative encodings for
---
> features, but they sometimes provide several alternative encodings for
605c600
< proposed by these Guidelines.</p></div4>
---
> that these Guides have.</p></div4>
886c881
< an updated version of these Guidelines which supported XML unambiguously. For example, because SGML
---
> an update to these Guidelines, to support XML unambiguously. For one example, because SGML
893,896c888,889
< undertaken. The goals of this update were to revise both the text and
< the DTDs of the scheme in a
< way compatible with use of either  SGML and
< XML. The
---
> undertaken, to provide an update of the DTDs that is compatible with both SGML and
> XML, and an update of these Guidelines that is also compatible with both. The
