Klotz, Leigh wrote:
> That's reassuring. So let's all take a look at Dave's proposals in that
> light -- an HTML enhancement that maps more directly onto the concepts
> that have been in the XForms Rec since 2003.
And yet I still haven't heard anyone explain to me why WF2 or a
successor thereo
On Jan 23, 2007, at 23:48, liorean wrote:
If the DTD allows it on all elements,
There's no DTD.
you can put
xml:space="preserve" on all elements in the document that need it for
the tools that don't use the external subset or namespace recognition
The start of this thread was about getting
On 1/23/07, Henri Sivonen <[EMAIL PROTECTED]> wrote:
On Jan 23, 2007, at 17:45, liorean wrote:
> Well, considering the purpose of XHTML (main purpose is presentation
> for humans, no?) is there any reason to NOT just set it to default to
> "preserve" on the html element, fixed to "preserve" on th
On Jan 23, 2007, at 23:15, Martin Atkins wrote:
Presumably its primary purpose is to act as a signal to generic XML
tools — that don't have any special knowledge about XHTML — that
they should not screw around with the whitespace inside PRE, etc.
Exactly.
On Jan 23, 2007, at 17:45, liorean
Anne van Kesteren wrote:
xml:space can't affect the tree being formed as far as I know. It's not
entirely clear to me what its use is anyway, except in SVG, where they
defined it in a funny way to make it do something.
Presumably its primary purpose is to act as a signal to generic XML
to
Anne,
That's reassuring. So let's all take a look at Dave's proposals in that
light -- an HTML enhancement that maps more directly onto the concepts
that have been in the XForms Rec since 2003.
Leigh.
-Original Message-
From: Anne van Kesteren [mailto:[EMAIL PROTECTED]
Sent: Tuesday, Ja
On Tue, 23 Jan 2007 13:51:55 -0500, Klotz, Leigh <[EMAIL PROTECTED]>
wrote:
Or what makes you want to cannibalize an existing W3C Recommendation
which predates the formation of WHAT-WG?
I don't think most people in the WHATWG see it as a XForms versus Web
Forms 2 "match" or something. I don'
Or what makes you want to cannibalize an existing W3C Recommendation
which predates the formation of WHAT-WG?
> Explain to me why Web Forms 2.0 shouldn't be "incorporating more of
the great ideas" in XForms-Tiny rather than the other way around. Why is
your approach to cannibalize an existing W3C
On 1/23/07, Anne van Kesteren <[EMAIL PROTECTED]> wrote:
xml:space can't affect the tree being formed as far as I know. It's not
entirely clear to me what its use is anyway, except in SVG, where they
defined it in a funny way to make it do something.
Hmm, reading the relevant part of the XML1.0
On Tue, 23 Jan 2007 10:45:15 -0500, liorean <[EMAIL PROTECTED]> wrote:
Well, considering the purpose of XHTML (main purpose is presentation
for humans, no?) is there any reason to NOT just set it to default to
"preserve" on the html element, fixed to "preserve" on the script,
style, pre and texta
On 1/23/07, Henri Sivonen <[EMAIL PROTECTED]> wrote:
On Jan 22, 2007, at 23:57, Ian Hickson wrote:
> It's automatically conforming everywhere, no? Isn't it an XML thing?
It is an XML thing. XML 1.0 4th ed. says:
> A special attribute named xml:space may be attached to an element
> to signal an in
On Jan 22, 2007, at 23:57, Ian Hickson wrote:
It's automatically conforming everywhere, no? Isn't it an XML thing?
It is an XML thing. XML 1.0 4th ed. says:
A special attribute named xml:space may be attached to an element
to signal an intention that in that element, white space should be
12 matches
Mail list logo