On Sun, 19 Mar 2006, Henri Sivonen wrote:
Since U+ has no legitimate reason to be there just to get dropped,
is any encounter of U+ a parse error?
Yes. Fixed.
The way the spec is written, U+000D does not occur in the character
stream immediately before tokenization, but (as in
On Mar 11, 2006, at 03:21, Ian Hickson wrote:
On Sat, 25 Feb 2006, Henri Sivonen wrote:
On Feb 25, 2006, at 02:02, Ian Hickson wrote:
On Sat, 23 Jul 2005, Henri Sivonen wrote:
Which characters should a text/html HTML5 conformance checker
consider
forbidden? The same characters that are
On Sat, 23 Jul 2005, Henri Sivonen wrote:
Which characters should a text/html HTML5 conformance checker consider
forbidden? The same characters that are forbidden in XML 1.0 (\0, FF,
etc.)? Or some other set?
In what context?
--
Ian Hickson U+1047E
Which characters should a text/html HTML5 conformance checker consider
forbidden? The same characters that are forbidden in XML 1.0 (\0, FF,
etc.)? Or some other set?
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
