On Tue, 30 Oct 2007, Krzysztof Żelechowski wrote:
Because lang in no namespace is what is normal for HTML. However,
since Anne said UAs have already implemented xml:lang taking
precedence, I guess it is best to go with what is implemented.
Well, xml:lang is what is normal for
On Mar 11, 2006, at 16:17, Simon Pieters wrote:
From: Henri Sivonen [EMAIL PROTECTED]
Shouldn't lang take precedence in HTML?
Why should the lang attribute (in the null namespace) take
precedence in HTML?
Because lang in no namespace is what is normal for HTML. However,
since Anne said
On Mar 11, 2006, at 03:20, Ian Hickson wrote:
On Sun, 19 Feb 2006, Henri Sivonen wrote:
Off the top of my head, the changes from the HTML parsing output
involve
(besides lowercasing names and putting elements in the XHTML 1.x
namespace)
getting rid of the meta element conveying character
Hi,
From: Henri Sivonen [EMAIL PROTECTED]
BTW, the spec also says: If both the xml:lang attribute and the lang
attribute are set, user agents must use the xml:lang attribute, and the
lang attribute must be ignored for the purposes of determining the
element's language.
Shouldn't lang
On Sun, 19 Feb 2006, Henri Sivonen wrote:
Off the top of my head, the changes from the HTML parsing output involve
(besides lowercasing names and putting elements in the XHTML 1.x namespace)
getting rid of the meta element conveying character encoding information,
Why? It doesn't need to be
On Feb 16, 2006, at 00:56, Dan Brickley wrote:
Discussing some related work (GRDDL) in the W3C SemWeb CG, I was
wondering whether there is any way your parser spec could be
specified as input for a GRDDL transform. GRDDL provides techniques
for
transforming XML-based languages (including
On Thu, 16 Feb 2006, Dan Brickley wrote:
Ah. Well, HTML5 is defined in terms of a DOM, so GRDDL is presumably,
therefore, already supported.
Once you pick a serialization (or we do, for GRDDL), I guess so. Is
there a shopping list of DOM serialization candidates around somewhere?
On Tue, 14 Feb 2006, Rory Parle wrote:
In section 8.2.1. Tokenisation, should the sentence Command and
character tokens have data read Comment and character tokens have
data?
Good catch, thanks. Fixed.
--
Ian Hickson U+1047E)\._.,--,'``.fL
On Wed, 15 Feb 2006, Dan Brickley wrote:
Have you considered defining the parser behaviour in terms of XML
concepts?
What would that mean?
Could you give an example of what that would look like?
If you do get to the test suite stage, there'll be need for some
concrete syntax presumably,
On Wed, 15 Feb 2006, Dan Brickley wrote:
* Ian Hickson [EMAIL PROTECTED] [2006-02-15 23:02+]
On Wed, 15 Feb 2006, Dan Brickley wrote:
Have you considered defining the parser behaviour in terms of XML
concepts?
What would that mean?
Could you give an example of what that
* Ian Hickson [EMAIL PROTECTED] [2006-02-15 23:02+]
On Wed, 15 Feb 2006, Dan Brickley wrote:
Have you considered defining the parser behaviour in terms of XML
concepts?
What would that mean?
Could you give an example of what that would look like?
Expressing things in terms of
* Ian Hickson [EMAIL PROTECTED] [2006-02-13 22:07+]
So...
The first draft of the HTML5 Parsing spec is ready.
I plan to start implementing it at some point in the next few months, to
see how well it fares.
Any plans for a test suite? eg. pairs of input files and normalised
output?
+cc: Dan Connolly
* Ian Hickson [EMAIL PROTECTED] [2006-02-14 18:41+]
On Mon, 13 Feb 2006, Dan Brickley wrote:
Any plans for a test suite? eg. pairs of input files and normalised
output? (if that makes sense...).
I'd strongly recommend people put off creating a test suite until
Quoting Ian Hickson [EMAIL PROTECTED]:
The first draft of the HTML5 Parsing spec is ready.
Great!
It's not 100% complete. Some of the things that need work are:
Interaction with document.open/write/close is undefined
How to determine the character encoding
Integration with quirks
Ian Hickson wrote:
So...
The first draft of the HTML5 Parsing spec is ready.
[...]
In section 8.2.1. Tokenisation, should the sentence Command and
character tokens have data read Comment and character tokens have
data?
On Mon, 13 Feb 2006, Dan Brickley wrote:
Any plans for a test suite? eg. pairs of input files and normalised
output? (if that makes sense...).
I'd strongly recommend people put off creating a test suite until the spec
is in more than a first draft, but yes, on the long term this is
On Tue, 14 Feb 2006, Alexey Feldgendler wrote:
It's not 100% complete. Some of the things that need work are:
Interaction with the load event is undefined
What's that for? I think it shouldn't be defined in the parsing spec.
Well, it's not strictly part of the parser section I
On Tue, 14 Feb 2006, Anne van Kesteren wrote:
However, none of the above are particularly critical to the parsing.
Attribute parsing is. And there are some special cases made for that
here and there. It would be good if that was specified as well.
Oh, crap, forgot about those. I even
So...
The first draft of the HTML5 Parsing spec is ready.
I plan to start implementing it at some point in the next few months, to
see how well it fares.
It is, in theory, more compatible with IE than Safari, Mozilla, and Opera,
but there are places where it makes intentional deviations
On Tue, 14 Feb 2006 04:07:03 +0600, Ian Hickson [EMAIL PROTECTED] wrote:
The first draft of the HTML5 Parsing spec is ready.
I think I'll have time to review it this week. Maybe I'll make a
proof-of-concept implementation in some scripting language.
It's not 100% complete. Some of the
20 matches
Mail list logo
