W3C home > Mailing lists > Public > public-html@w3.org > November 2009

Re: XHTML character entity support

From: Maciej Stachowiak <mjs@apple.com>
Date: Sat, 31 Oct 2009 18:33:07 -0700
Cc: Boris Zbarsky <bzbarsky@mit.edu>, Alexey Proskuryakov <ap@webkit.org>, HTML WG <public-html@w3.org>
Message-id: <46A567D7-81CF-459E-90F5-F2A160AA6D48@apple.com>
To: Shelley Powers <shelley.just@gmail.com>

On Oct 31, 2009, at 6:22 PM, Shelley Powers wrote:

> Yes, how the browsers work when it comes to DTDs and named entities
> has come up in the past [1][2].
> Case in point, Firefox, Safari, and Chrome don't allow named entities
> in XHTML+RDFa documents, even though the XHTML+RDFa DTD does reference
> the named entities.
> Oops
> But, still, we manage. We use numeric entities.

I think it's fine to omit named entities from newly minted DTDs. In  
fact, probably a good idea since it's the strict XML behavior and  
nothing stops you from using an NCR or just a literal unicode  
character in new content.

But browsers need to handle named entities when some specific XHTML  
DTDs are present, since there is a body of legacy content that depends  
on having the XHTML set of entities. Handling content with the XHTML 
+RDFa DTD does not have this constraint.

Note: we'd rather not have this behavior in WebKit but we added it due  
to compatibility bugs being filed. I expect any XHTML-capable browser  
would eventually be pressured to add similar behavior. Non-browser  
tools that process XHTML from the Web may also benefit from doing the  
same thing.

Received on Sunday, 1 November 2009 01:33:48 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:02 UTC