If xslt processing is going to be done in the final user machine, we should not expect the user have even Java. And Inkscape is already dependent upon libxml2/libxslt (am I wrong?). So, it seems there are three things that can be done:
1.- Have the user to install Java and Saxon to see the documentation.
2.- Achieve the same things that Java and Saxon do using libxslt and some extension module.
3.- Pregenerate all the svg help files and use them pregenerated, as is being done till now.
I'm not very fond of 1. Using 3 excludes the option of a thin format for documenting extensions (perhaps as part of .inx files).
So I'm going to look closer at 2. At this moment, I have a single question:
1.- If the saxon stuff is implemented and a workaround for invoking Inkscape and getting paragraph height is found, libxslt already implements enough of the standard to be of use?
On 6/22/06, bulia byak <buliabyak@...400...> wrote:
On 6/22/06, Bob Jamison <rwjj@...127...> wrote:
> So unless Saxon provides some special functionality, this might be an
> unnecessary lib.
There are two things that make it possible to generate SVG only via
Saxon (if you can propose a better and more general method, you are
welcome):
1. saxon:assign
2. running external java class org.inkscape.xslt.files with methods
for checking for existence of files and for running external process
(inkscape) and returning its output
There's also saxon:function but this one should be easier to work
around (especially if we use XSLT 2.0).
--
bulia byak
Inkscape. Draw Freely.
http://www.inkscape.org
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
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel