> While it might be possible to create an HTML-like specification in which
> the markup and the content could potential be in different encodings (with
> some constraints: you need to avoid byte sequences in content that can be
> wrongly interpreted as markup), this is no the case for HTML or for XML:
> the entire file, markup and content, must be in the same encoding.
This is true for HTML, and true as far as it goes for XML. However,
an XML document may contain multiple entities (files), and each of
these can be in its own encoding.
-- There is / one art || John Cowan <email@example.com> no more / no less || http://www.reutershealth.com to do / all things || http://www.ccil.org/~cowan with art- / lessness \\ -- Piet Hein
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:18 EDT