W3C home > Mailing lists > Public > www-svg@w3.org > January 2006

Re: SVGT 1.2: A proposal for how to define SVG whitespace in terms of CSS whitespace

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Tue, 31 Jan 2006 04:14:58 +0100
To: Maciej Stachowiak <mjs@apple.com>
Cc: www-svg@w3.org
Message-ID: <m7ltt150uiaqqct9v3g68uvaphg20hvge2@hive.bjoern.hoehrmann.de>

* Maciej Stachowiak wrote:
>I that case, here's some alternate proposals:
>
>A) When xml:space is not specified, the document should be preserve  
>all whitespace, and in general act as specified for  
>xml:space="preserve".

You should say what you mean by "preserve", should it be in the DOM,
should you see it in the rendering, how does it look like, etc.

>B) SVG could add a DTD or some other mechanism to set a default value  
>for the attribute.

I gather people dislike when things magically appear in the DOM. On the
other hand, as I read the SVG Tiny 1.2 draft, getAttributeNS will return
"default" values whenever attributes are not specified, and hasAttribute
is not part of the DOM subset, so the people who dislike that might have
a problem...

>C) If xml:space="default" is defined to not modify the text in the  
>DOM but only apply styling, then there is no need to set a default  
>value or define what any of the values do to parsing.

Yes, xml:space has no effect whatsoever on what's in the DOM. That's
only a myth spread by the HTML Working Group, as far as I can tell,
all SVG says is how the attribute affects SVG processing in terms of
rendering and some APIs.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Tuesday, 31 January 2006 03:14:08 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:33 GMT