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

https://www.w3.org/Bugs/Public/show_bug.cgi?id=13409

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

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

--- Comment #7 from David Carlisle <davidc@nag.co.uk> 2011-12-22 19:08:27 UTC ---
(In reply to comment #6)

> Status: Rejected
> Change Description: no spec change
> Rationale: If the argument is that we should add URLs to the list of magic DTD
> URLs in the spec, then I'm happy to do that; all you have to do is show that
> the URL you want to add already works in the majority of deployed browsers.
> 
> Other than that, the premise of this bug seems incorrect, as Henri has noted.


Reopening. Holding off from the somewhat adversarial escalation process for
now, but may choose to do that later.

As noted in earlier comments this change broke existing pages (for those
implementations that supported MathML entities previously) such as Firefox
(prior to 4) and IE/MathPlayer.

For example

http://www.w3.org/TR/2010/PR-MathML3-20100810/chapter2.xml

rendered in all relevant browsers at the time it was published but fails with a
fatal parse error if processed according to the current html spec.

The XHTML version of the final MathML3 rec broke in the same way, but we edited
that one in place to work around this unresolved bug, removing the entity
references.

The current spec makes it impossible to use the doctype to specify processing
relevant to current documents for the xml toolchain, while still allowing the
file to be parsed by an xhtml system.

Any fixed list would have similar defects although of course extending it would
patch individual cases. 

My preference would be to specify that the data url with the entity definitions
be loaded for any DOCTYPE with a PUBLIC id for a page served as
application/xhtml+xml

This would allow easy use of catalogs to gain the same behaviour in standard
xml toolchains, and would still allow an easy way for page authors to avoid the
cost of entity processing, by not using a public ID or by using (say)
application/xml.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 22 December 2011 19:08:32 UTC