On 27/09/2006 11:23 AM, Ian Hickson wrote:
The problem with adding entities is that a LOT of people do things like
href="/u?aa=foo&ab=foo&ac=foo&ad=foo"
...which today works, but would break if MathML entities were introduced
(since &ac is a MathML entity).
That list is so big that trying to hand-pick some and leaving some out
would need another committee...
Is is okay to assume HTML5 (with its <!DOCTYPE html>) as supporting all
W3C entities _by default_?
Don't do anything based on the DOCTYPE. HTML5 is anything sent as
text/html.
I thought the DOCTYPE was trustworthy -- based on this excerpt from the
HTML5 spec:
"HTML documents that use the new features described in this
specification must start with the string <!DOCTYPE html> and, if they
are served over the wire (e.g. by HTTP) must be labelled with the
text/html MIME type."
If so, it would have meant less conflicts with agreed entities in HTML5.
BTW, for my own information, do you intent HTML5 to be transitional,
almost-standards, or strict? If it is HTML5 (or XHTML5) served as
text/html but put in the XHTML namespace at some later stage (as the
HTML5 implies), it better be strict, no? And that would be driven by the
DOCTYPE detection code. Catch my drift? Or is tag soup going to be in
the XHTML namespace?
If it is strict then maybe entities could be required to have a
semi-colon -- which will then avoid the ambiguities you mentioned above.
Not that I have a position on this (at least as yet). I am just bringing
in some food for thoughts, to accommodate the realistic issues of MathML.
---
RBS
_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout
