Publishing in SVG

Rick <[email protected]>
Newsgroups gmane.text.doxygen.devel
Message-ID <[email protected]>
Hello all.

First of all let me state that doxygen rocks!  I'll leave it at there
since you all know that.

I have a question, I wasn't sure whether to post this on the user list
or this list.  I picked this one.

To cut to the quick, I'd like to publish docs in SVG.

more detail...

I'm developing a platform that is basically an internet SVG
presentation layer.  SVG is a W3C xml vector graphics standard that
can be compared in many ways to Flash.  SVG is XML.  The client is a
web broswer, supporting SVG either natively, or via a plugin.  We are
developing a viewer, as a plugin initially, and eventually there will
be a standalone client.

The backend runs on a Linux server, or servers, and leverages Apache
as an internet gateway.

The server suite will act as a host for application services.

User documentation, with the exception of setup and troubleshooting,
will be published in SVG, naturally, since that is the client
interface.

Backend documentation, the API, could benefit from being published in
SVG as well, and this is where my question arises.

I will publish the API through doxygen, and most certainly in HTML and
(ugh) Word.  I'd like to coerce it to publish SVG.

My first thought is to just take the HTML ouput and post-process it,
and this I can surely do.

I don't know much about how doxygen works, which is a testament to its
excellence, I don't need to.

Is there a better way?


zz
-- 
Cheers!
Rick

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.