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

Re: SVG 1.2 Comment: 4 Flowing text and graphics

From: Denis Bohm <denis@fireflydesign.com>
Date: Wed, 3 Nov 2004 18:58:28 -0800
Message-ID: <004d01c4c21a$3f8426a0$71307f42@DRAGONFLY>
To: "Ian Hickson" <ian@hixie.ch>, "Thomas DeWeese" <Thomas.DeWeese@Kodak.com>
Cc: <www-svg@w3.org>

> > > It seems bad to me to be requiring a lowest-common-denominator
> > > algorithm for line breaking.
> >
> > This is because you don't care about graphical interoperability between
> > user-agents.  This is exactly why it's appropriate for the SVG WG (where
> > this is extremely important) to define this.
> I do not understand why it is important for SVG rendering agents to all
> have the same line breaking.

That seems to be the whole issue with this long thread.  SVG is presentation
level - it is defined so that the output is consistent in all
implementations.  That is what SVG is all about.  If you don't want
presentation level then you need to use some other representation (and
possibly a transformation into SVG to view it).

> The whole point of user-agent controlled line
> wrapping is that the line wraps where it needs to wrap, and not in a
> necessarily precise location. If the precise location was important, the
> author would use manual line breaking.

That's the point in HTML, but not in SVG.  The point of line wrapping in SVG
is to have it reproducible and keep the intent of the author so that isn't
lost via manual breaking (or obscured by using proprietary meta tags).
Received on Thursday, 4 November 2004 02:59:43 UTC

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