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

SVG 1.2 General feedback

From: Jim Ley <jim@jibbering.com>
Date: Sun, 17 Nov 2002 13:23:47 -0000
Message-ID: <01b001c28e42$9334ec20$1a3c70c2@7020CT>
To: <www-svg@w3.org>


This is some short general feedback on various areas, more specific
feedback on the SVG window interface will follow.

"preformatted" in 1.5
|'preformatted' This has the sole effect of turning off the suppression
|of non-printing (white space) characters at the start of a line.

If there's going to be such an attribute, (and I'd fall on the side of
not) then why does it only do whitespace at the start of the line - why
not end, or in middle?  Also I may be mis-remembering here, and I should
check first, but does not XML allow the XML application to discard leading
whitespace - meaning preformatted may be impossible?

1.10 Text Flow
  I'd like a hyphenation engine to be an allowable extension, but
obviously not required, but if a viewer did decide to implement it, I
would still like it to be conformant and not need extensions.

2.1  A default rendering would be very nice, it's not always desirable to
spend time developing a UI widget, and it is best for understanding if we
can have consistency between different applications where it's
appropriate.  I also like the idea that there's a stable default rendering
that users who don't understand a particular authors scheme can "switch

6.2 Background fill - I'm not sure I like the idea of a pattern being
fixed against user-pan, if we have a hatched background and the user pans,
I think it might feel odd to not have the hatches "move", perhaps there
could be an attribute to define the behaviour, if it's possible of course.

7.1 DOM access to images - Some image formats allow multiple XML documents
to be included (e.g. Adobe's XMP can have multiple, or live alongside
EXIF) it would be nice if we could make all available, but if not the spec
should specify which (the "first" presumably.)

Also - since SVG 1.2 is an early draft, and sending in typos can be
considerable, would it be a good idea to use  an Annotea interface
(presumably using annotest.w3.org ) to highlight typos, rather than
sending them to the list? (text-index/text-indent jumped out immediately
for example)


Received on Sunday, 17 November 2002 09:07:18 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:46:54 UTC