[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: UTF-8+names

• To: xml-dev@l...
• Subject: Re: UTF-8+names
• From: Miles Sabin <miles@m...>
• Date: Sun, 19 Oct 2003 21:59:00 +0100
• In-reply-to: <3F92F00E.50603@t...>
• References: <20031019034635.91162.qmail@w...> <200310192101.05193.miles@m...> <3F92F00E.50603@t...>
• Sender: Miles Sabin <miles@m...>
• User-agent: KMail/1.5.4

Tim Bray wrote,
> Miles Sabin wrote:
> >   <?xml encoding&=;"UTF-8+names"?>
> >
> > How would that get along with Appendix F style encoding detection?
>
> Since there is no replacement named '&=;', this would be passed to
> the XML processor exactly as you see it there.  The XML processor
> would (correctly) throw it on the floor, because it's not
> well-formed. Where's the problem? -Tim

OK, my mistake. I misread section 4 (I missed the fact that the '&' and 
';' would be passed through too).

But looking through the list of MathML named entities[1] it looks as 
tho' there's plenty there which could cause a lot of trouble in an 
encoding declaration. Aside from the XML magic five and the MathML 
whitespace entities, how about,

  <?xml encoding&equals;"UTF-8+names"?>
  <?xml version="1&dot;0" encoding="UTF-8+names"?>
  <?xml encoding="UTF-8&plus;names"?>

So I think we need a complete list of the predefined entities from XHTML 
and MathML which _aren't_ covered by sections 6 and 7. 

Cheers,


Miles

[1] http://www.w3.org/TR/MathML2/bycodes.html

• Follow-Ups:
  • Re: UTF-8+names
    • From: Miles Sabin <miles@m...>

• References:
  • Re: UTF-8+names
    • From: Mike Champion <mc@x...>
  • Re: UTF-8+names
    • From: Miles Sabin <miles@m...>
  • Re: UTF-8+names
    • From: Tim Bray <tbray@t...>

• Prev by Date: Re: UTF-8+names
• Next by Date: Re: UTF-8+names
• Previous by thread: Re: UTF-8+names
• Next by thread: Re: UTF-8+names
• Index(es):
  • Date
  • Thread