Re: [Refdb-users] User feedback 3

[David N. <dav...@bi...>]

Hi Markus,

>Thanks for that. I've added refdbxmlrc with some cosmetic changes to
>CVS. I've also integrated your refdbxml changes into the official
>version which also required some Makefile.am and configure.in
>hacking. I've fixed a few obvious typos in the file you sent and made
>some minor changes, like parametrizing the xep root variable.
>

I missed something very obvious that would remove the need to 
parameterise xep's root variable: the install process creates a shell 
script: 'xep.sh'.  It contains a customised launch command including 
classpath and ROOT parameters appropriate for that computer.  Here, for 
example, is the shell script as built on my system during the xep 
install process:

..........................................................................................................................
#!/bin/sh

# This script encapsulates a standard XEP call.

JAVA_HOME=/usr/local/java/j2sdk1.4.2_03/jre

XEP_HOME=/home/david/progs/apps/xep

CP=$JAVA_HOME/lib/tools.jar:$XEP_HOME/lib/xep374_trial.jar:$XEP_HOME/lib/saxon.jar:$XEP_HOME/lib/xt.jar

$JAVA_HOME/bin/java -classpath $CP com.renderx.xep.XSLDriver 
-DROOT=$XEP_HOME $*
..........................................................................................................................

Providing xep.sh is on the system path, xep can be invoked in 
process_print thus:

    xep.sh -fo $1 -pdf $2

This would remove the need to specify xep's root directory.

The only potential problem is that the installer does not place xep.sh 
in a standard system directory, like /usr/local/bin or /usr/bin.  IMO, 
however, that can rightfully be considered part of the xep install 
process rather than part of the refdb configure process.  If you changed 
the xep launch command to use xep.sh, perhaps a note in the init file 
could indicate the need to make sure xep.sh is on the system path?

Regards,
David.