ASCII output from XML
Egon Willighagen
egonw at subdimension.com
Mon Mar 12 16:23:33 CET 2001
Op maandag 12 maart 2001 12:55, schreef Wytze van der Raay:
> > I guess we should do this during configure. We've got to tweak
> > configure.in to handle something like
> >
> > configure --with-xercesjar=$HOME/lib/java/xerces-1.3.0.jar
> > --with-xalanjar=$HOME/lib/java/xalan-1.2.2.jar
Ok, that could a solution. However i was more thinking about extending
the configure.in to look for these jars itself... since it is able to find
libraries and executables... is this also possible?
An other possibility is to ship these two jars ourselves... and just look
for the java runtime executable... i know there are configure scripts to
look for 'java'...
> > lr_generate_ascii could be generated from a lr_generate_ascii.in,
> > expanding macro's like @PATHTOXERCESJAR@ and @PATHTOXALANJAR at .
Yes, that would be the idea.
> I presume this will be an additional *option* when installing LIRE on
> one's system? I.e. I think it should be possible to continue using LIRE
> on a system *without* having to inflate its footprint by a mandatory
> installation of JDK 1.2, xerces 1.3, xalan 1.2 and what else may come up.
> Of course you will miss the XML capability in that case, but initial
> adoption will be much quicker and simpler.
When i was extending the README yesterday is also saw that their is
a C version of Xalan... this we could ship and then we would not need Java
at all.... i haven't tested it yet, but i expect it to be of the same quality
of the Java version of this XSLT processor...
Egon
--
To UNSUBSCRIBE, email to development-request at logreport.org with a subject of
"unsubscribe". Trouble? Send an email with subject "help" to
development-request at logreport.org
More information about the Development
mailing list