Henri Sivonen wrote:
On Jan 26, 2005, at 23:53, Robert Sayre wrote:
Henri Sivonen wrote:
But if you can always substitute type='TEXT' with type='XHTML' but not the other way round, what's the point of having type='TEXT' in the spec?
You can't.
<title type='TEXT'>I&nbsp;do&nbsp;not&nbsp;like&nbsp;< marquee></title>
<title type='TEXT'>I do not like ...</title>
Sorry, I don't understand what your example is demonstrating.
How would the above be different from:
<title type='XHTML'>I&nbsp;do&nbsp;not&nbsp;like&nbsp;< marquee></title>
<title type='XHTML'>I do not like ...</title>
Oop, sorry. I pasted the first example in from one of the other times this has cropped up.
<title type='XHTML'>I do not like ...</title> <title type='TEXT'>I do not like ...</title>
Well I'll be damned. The spec says whitespace collapsing is allowed.
But guess what, "TEXT" is *never* coming out of the spec, because it will eventually become impossible to write something that looks like markup if we don't have it. If we were to choose between the two, we should eliminate XHTML.
Robert Sayre
