On Fri, May 14, 2010 at 5:23 PM, Aleksey Zapparov <i...@member.fsf.org> wrote:
> Hello,
>
> As far as I can see it's valid, but not very recommended. Or my english is
> not good enogh :)) XHTML 1.0 states:
>
> If it encounters an entity reference (other than one of the entities defined 
> in
> this recommendation or in the XML recommendation) for which the user agent
> has processed no declaration (which could happen if the declaration is in the
> external subset which the user agent hasn't read), the entity reference should
> be processed as the characters (starting with the ampersand and ending with
> the semi-colon) that make up the entity reference.
>
> And XHTML DTD has nbsp entity reference as:
>
> <!ENTITY nbsp   "&#160;">
>
> Correct me if I'm wrong or misunderstanding something...
>
>

Your e-mail prompted me to dig a little deeper. I had missed the fact
that the XHTML DTD imports an external entity reference that includes
nbsp. (I had initially just scanned the DTD itself for the entity.)
This was compounded by the fact that the <?xml ... ?> declaration I
had at the top of the layout inadvertently included standalone="yes"
which was causing Firefox not to resolve those external entity
references. I changed to <?xml version="1.0" standalone="no"
encoding="UTF-8" ?> and now the site appears to be working in Firefox
(3.6.3), Google Chrome (4.1), Opera (10.53), Safari (4.0.5) and even
Internet Explorer 7, all  using the application/xhtml+xml mime-type. I
guess support is getting better than I thought it was at this point.


Andrew

Reply via email to