W3C home > Mailing lists > Public > www-svg@w3.org > November 2004

Re: Towards resolution of SVG 1.2 Flowing text

From: Dean Jackson <dean@w3.org>
Date: Wed, 3 Nov 2004 03:50:10 +1100
Message-Id: <427A7AE9-2CEF-11D9-A2F5-000393B3CA5E@w3.org>
Cc: www-svg@w3.org
To: "Robert O'Callahan" <robert@ocallahan.org>

On 3 Nov 2004, at 02:42, Robert O'Callahan wrote:

> I have a couple of additional questions for the SVG WG:
> -- When users ask for additional flowing text features, such as floats 
> and tables, will you add them to SVG 1.3?

Let me separate the question a little.

We discussed adding additional text features (for SVG 1.2 and
future). We rejected them all in favour of using XHTML for such things
(eg. lists). As SVG layout is not at all like CSS layout, floats are
way out of scope.

Then you mentioned tables. There have been many requests for
grid-based layout mechanisms in SVG (for graphics and text). It *may*
be considered for a future version of SVG. However, IMO the primary use
case would be laying out things like UIs (eg. toolbars), not really
text (although it could be used that way). In preliminary discussion
of this topic the most common suggestion has been to simply allow
<html:table> in SVG. Adobe's most recent SVG release does this
(within a <foreignObject>).

> -- You say that SVG text is presentational and not semantic, but then 
> why does flowPara exist?

I don't think it should. I'll be arguing that it should be removed.

The other slightly semantic element is <flowLine>. The problem here
is that Ian's suggested alternative used CSS, which isn't required
in any SVG implementation. Any ideas?

Received on Tuesday, 2 November 2004 16:50:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:01 UTC