Re: [docbook-apps] Xalan, document(), and chunker.output.intent [WAS: base.dir param...]

[Michael Smith <smith@xml-doc.org>]

Larry Garfield <larry@garfieldtech.com> writes:

[...]

> As for Saxon, ugh. :-)  I hate switching packages around, mostly because 
> Java packages are such a pain to setup in my experience. [...]

You're running Debian, right? Or some Debian-based system. If so,
there only setup you need to do to use Saxon is to apt-get it:

  apt-get install libsaxon-java

The info on using it is all in Bob's book.

Yeah, I guess there is the fact that you do also need to tell java
where it is, by putting it into your CLASSPATH or whatever. But
that doesn't seem to me like such a big pain. A lot of people just
create a script to use it -

  #!/bin/sh

  SAXON=/usr/share/java/saxon.jar
  DOCBOOKXSL=/usr/share/xml/docbook/stylesheet/nwalsh

  java -cp $SAXON:$CLASSPATH \
    com.icl.saxon.StyleSheet $1 $DOCBOOKXSL/$2

Call it "saxon" or whatever and put it in your path. Then you can
process DocBook docs with it just by doing, for example:

  saxon foo.xml xhtml/chunk.xsl
  saxon foo.xml fo/docbook.xsl
  saxon foo.xml manpages/docbook.xsl

IMHO, you're better off using Saxon than Xalan2. There are
definitely no known issues with using Saxon to process DocBook.
I'm not sure that the same is true about Xalan2. There have been
some Xalan2 bugs in the past that have caused problems when using
it with DocBook. I'm not sure if those have all been resolved or
not. And if they're still doing releases of it, any new releases
have the potential to introduce a new bug. Saxon 6.5.3 is stable
and bug free and has everything you need as far as a Java-based
XSLT engine for DocBook processing goes.

  --Mike

> >----- Original Message ----- 
> >From: "Larry Garfield" <larry@garfieldtech.com>
> >To: <docbook-apps@lists.oasis-open.org>
> >Sent: Thursday, March 24, 2005 11:14 PM
> >Subject: Re: [docbook-apps] base.dir param not working in customization
> >layer
> >
> >
> >
> >>And I'd even tried the single-quotes to fix a different param issue I
> >>was having and didn't think of it here. :-)  That did it, thanks!
> >>
> >>On a related note, I'm having a similar problem with the
> >>chunker.output.indent parameter being ignored.  Whether it's set via the
> >>customization file or command line, I still get a line break-free output
> >>file.  (This is the one where I DID try putting "yes" in quotes, and it
> >>still didn't work, yet didn't think to try that on the base.dir as well.
> >><g>)  Would that be a related issue?
> 

-- 
Michael Smith
http://logopoeia.com/  http://www.oreillynet.com/pub/au/890

smime.p7s