Pablo Rodríguez | 23 Jul 2012 19:56
Picon

Re: some basic questions on how to work with TEI

On 23/07/12 19:24, Sebastian Rahtz wrote:
> [...]
> what is the content of /usr/bin/saxon?
> 
> ie
> 
>   cat /usr/bin/saxon

$ cat /usr/bin/saxon
#!/bin/sh
#
# saxon script
# JPackage Project <http://www.jpackage.org/>

. /usr/share/java-utils/java-functions

MAIN_CLASS=net.sf.saxon.Transform

BASE_JARS="saxon.jar xml-commons-apis.jar jaxp_parser_impl.jar
bea-stax-api.jar bea-stax-ri.jar"

# Optional jars
CLASSPATH="$CLASSPATH:"$(build-classpath docbook-xsl-saxon \
  avalon-logkit xml-commons-resolver 2>/dev/null) || :

# If we have resolver, add the CatalogManager.properties dir to CLASSPATH,
# and tweak command line options so that it's used.
args=
if echo "$CLASSPATH" | grep xml-commons-resolver >/dev/null 2>&1 ; then
  CLASSPATH="$CLASSPATH:/etc/java/resolver"
(Continue reading)

Sebastian Rahtz | 23 Jul 2012 21:19
Picon
Picon
Favicon

Re: some basic questions on how to work with TEI

On 23 Jul 2012, at 18:56, Pablo Rodríguez wrote:
> #
> # saxon script
> # JPackage Project <http://www.jpackage.org/>
> 
> . /usr/share/java-utils/java-functions
> 
> MAIN_CLASS=net.sf.saxon.Transform
> 
> BASE_JARS="saxon.jar xml-commons-apis.jar jaxp_parser_impl.jar
> bea-stax-api.jar bea-stax-ri.jar"
...

oh my lord, I dont know what they are up to here. this does not look
like the simple default Saxon jar at all.

you definitely need a Fedora sort of person!

I am sorry this is all proving so hard for you. It really should be easier!
But doing stuff on a Linux command-line is, I fear, a dying art.
That's why the setup in OxGarage, and in oXygen, are really
better to use.

--
Sebastian Rahtz      
Head of Information and Support Group
Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

(Continue reading)

Pablo Rodríguez | 23 Jul 2012 22:49
Picon

Re: some basic questions on how to work with TEI

On 23/07/12 21:19, Sebastian Rahtz wrote:
> On 23 Jul 2012, at 18:56, Pablo Rodríguez wrote:
>> #
>> # saxon script
>> # JPackage Project <http://www.jpackage.org/>
>>
>> . /usr/share/java-utils/java-functions
>>
>> MAIN_CLASS=net.sf.saxon.Transform
>>
>> BASE_JARS="saxon.jar xml-commons-apis.jar jaxp_parser_impl.jar
>> bea-stax-api.jar bea-stax-ri.jar"
> ...
> 
> oh my lord, I dont know what they are up to here. this does not look
> like the simple default Saxon jar at all.

Many thanks for your your replies and your help, Sebastian.

Only a side question on the saxon script that invokes saxon. I guess
there is no problem with that script when I invoke the Ant task (since I
invoke the saxon.jar file itself).

> I am sorry this is all proving so hard for you. It really should be easier!
> But doing stuff on a Linux command-line is, I fear, a dying art.

This is partly what I asked for, I guess :-).

I'm not a command-line expert, but I'm afraid that cryptic (to me)
warning or error messages are some of the reasons because I tend to
(Continue reading)


Gmane