W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > November 2009

Re: Fwd: XHTML character entity support

From: Shelley Powers <shelley.just@gmail.com>
Date: Tue, 03 Nov 2009 14:02:41 +0000
Message-ID: <643cc0270911030602ua3ed47eo7b9b0ee90121fc67@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>
Cc: John Cowan <cowan@ccil.org>, "public-xml-core-wg@w3.org" <public-xml-core-wg@w3.org>, "public-html@w3.org" <public-html@w3.org>
On Tue, Nov 3, 2009 at 3:28 AM, Simon Pieters <simonp@opera.com> wrote:
> On Mon, 02 Nov 2009 20:41:24 +0100, John Cowan <cowan@ccil.org> wrote:
>
>> Simon Pieters scripsit:
>>
>>> What is being discussed is not adding predefined entities. What is being
>>> discussed is making certain doctypes map to DTDs that contain just entity
>>> declarations (which is what Firefox, WebKit and Opera do today).
>>
>> Well, any non-validating parser is free to do that today.  (It's not quite
>> clear to me from the XML Rec whether a validating parser is compelled
>> to actually read an external DTD subset, or whether it may simply assume
>> what it contains.)
>>
>> The downside is that some non-validating parsers, those that do not read
>> the external subset, will reject the document as not well-formed.
>
> Or they can fail to expand the entities without a fatal error (like Opera
> does). Either way, this is exactly the issue. If I understand Alexey
> correctly, he wants to remove the downside by having a requirement that UAs
> have the mapping for a handful of doctypes.
>
> --
> Simon Pieters
> Opera Software
>
>

Oops, again. Opera does generate an XML parsing failure when it comes
across an undefined entity when using the XHTML5 doctype.

It's only with Henri's test, with the bogus DTD that Opera fails.

Shelley

Shelley
Received on Tuesday, 3 November 2009 14:19:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:41 UTC