W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2012

[Bug 13409] Defining Entity references for characters in XHTML.

From: <bugzilla@jessica.w3.org>
Date: Tue, 16 Oct 2012 17:57:39 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-13409-2486-Np2tTCk10U@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13409

David Carlisle <davidc@nag.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |TrackerRequest
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |---

--- Comment #19 from David Carlisle <davidc@nag.co.uk> ---
reopening with TrackerRequest  advised. Closing because of comment is not
acceptable as comment 14, that this change is necessary for compatibility
reasons, is just demonstrably false. This is a change that was introduced in a
draft of the html5 spec that broke existing content using these entity
definitions, Not least the MathML spec as shown in comment 3.

Proposed title

Defining Entity references for characters in XHTML

proposed Text

The current status quo for application/xhtml+xml parsing is that:

If the document references entity definitions that define HTML-compatible
entities, the DTD reference is ignored, no entities are defined, and a fatal
error will occur if any character entitles are used.

If the document references one of the legacy HTML4 era DTD then the HTML5
compatible entity definitions are loaded but this makes the document content
change depending whether it is processed with a default xml parser or one
configured as per html5, which is a needless and dangerous incompatibility.


----------------------------------------------

Proposal is to allow _some_ method of specifying an HTML5 compatible entity set
in a way that causes the HTML5 entity definitions to be loaded.

The least-change option would be to add an additional PUBLIC identifier to the
existing list that would cause the same set to be loaded in an xml system.
However other possibilities are also possible.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 16 October 2012 17:57:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 16 October 2012 17:57:41 GMT