Re: SVG 1.2 General feedback

Vadim Plessky wrote:

 > He told me that "some things needs to be finished first" (and I fully
 > agree
 > here), but may be it worth to include info about XSVG in W3C matrix
 > (of SVG
 > implementations), so we will attract new developers?..

Yep, that is one good way for doing that.

 > Well, SVG is already incorporated into Linux. :-)
 > There are Sodipodi (http://sodipodi.sourceforge.net) and Karbon14
 > (http://www.koffice.org) vector-drawing applications, and both apps
 > are built
 > on top of SVG drawing primitives and XML format.

I meant at a lower, more general and more basic level, but the projects 
you list are all great :)

If you know of stuff that's not on
http://www.protocol7.com/svg-wiki/ow.asp?GnuLinux ,
please add it.

 > You can find sources at:
 > http://freetype.newmail.ru/svg/
 > you need
 > http://freetype.newmail.ru/svg/BlueSphere-0.2.1.tar.bz2

Great that you put them online :)

 > |  > I can just mention that I tested them
 > |  > (in addition to renderers on Linux) with Adobe SVG plugin on
 > |  > WIndows,
 > |  > and they are rendered ok.
 > |
 > |  In addition, I suggest to validate the SVG documents, with at least
 > |  > one
 > |  good validator (eg libxml's xmllint).
 >
 > Ah, you are right.
 > I wish I had time to do that

You can set up your editor so that you only need to hit one or two keys, 
and the current buffer or file gets validated. Or/and you can write 
simple scripts which do batch validation for you. I do both; after 
everything is set up using shortcuts and catalogs, you don't need any 
more time than split seconds :)

If you use Vim, you could dig around
http://www.pinkjuice.com/vim/

 > - but so far I hope that SVG files produced by
 > Sodipodi have valid XML.

The SVG files also need to be valid SVG ;)
Using tools tells you more than hoping.

 > Sodipodi uses libxml2, so I doubt that something is wrong with those
 > files.

They look OK, I'm not sure if they get validated though. Perhaps onSave? 
Anyways, I'm not sure at which version they are now, but some months 
ago, there were validity errors
http://groups.yahoo.com/group/svg-developers/message/21796
which they fixed as quick as lightning. (not after months as with most 
commercial products) Awesome people!

But if you publish SVGs, the safest thing is to validate the documents, 
no matter what creation tools you use.

 > (in that case, Sodipodi needs to be fixed)

Yep. But before they can be fixed, bugs need to be found, and reported. 
In order to find any bugs related to invalid output, you need to 
validate the SVGs.

 > |  > For example, Adobe SVG plugin freezes my WIndows from time t
 > |  > time.
 > |
 > |  Please submit bug reports at
 > |  http://www.adobe.com/svg/feedback/bugreport.html
 >
 > Well, I don't have much time at a moment, and I also think that
 > supporting
 > closed-source projects ( bug reports are part of QA process) is not
 > very good
 > idea.
 > Not that I would request everyone to open their code.
 > I just made my choice. I am with Open-Soorce.  :-)

Well, you use the ASV, so it's useful for you. You didn't have to pay 
for it, and a tiny bug report may not really be much more hassle than 
writing the above lines :)

You told the public about this specific issue, so you should at least 
also tell Adobe.

You will support SVG much more than closed-source.

Tobi

-- 
http://www.pinkjuice.com/

Received on Wednesday, 20 November 2002 16:54:00 UTC