Re: [docbook-apps] Collecting xref targets - very slow?

["Bob Stayton" <bobs@sagehill.net>]

1. Yes it is unusual to take that long.  I just processed my 1.7MB book 
with Saxon 6.5.5 with collect.xref.targets="only", and it took 19 seconds. 
With xsltproc it  took 18 seconds for the same test.

First thing is to try testing with the stock stylesheet instead of your 
customization layer. If the time is much shorter, then the customization 
needs to be investigated.

If that is not shorter, then I'm wondering if it is still processing the 
whole book for some reason.  There is one thing you can check.  When you 
run it, watch the screen to see if the message "Writing mydoctargets.db for 
book" appears earlier in the process, or at the end.  That message 
indicates it has finished writing the olink data and has gone on to 
processing the book for output.  If collect.xref.targets="only" and 
processing continues after that message appears, then something else is 
going on.

2.  The <?xml version="1.0" encoding="utf-8"?> output at the terminal is 
generated by saxon even if it doesn't output anything else.  It could be 
turned off if <xsl:output omit-xml-declaration="yes"/> were used in the 
stylesheet.  But you need the XML prolog for FO output, and since there is 
only one stylesheet for both purposes, it would not be good to omit it.  It 
is harmless and does not indicate a problem.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Peter Desjardins" <pdesjardins@supplyscape.com>
To: <docbook-apps@lists.oasis-open.org>
Sent: Friday, January 26, 2007 2:17 PM
Subject: [docbook-apps] Collecting xref targets - very slow?


I recently separated the publishing step in which I generate xref
targets from the actual document generation.  It is now apparent that
collecting the xref targets accounts for the majority of the processing
time in my publishing process.  I have two questions about processing a
DocBook document to collect xref targets:

1. Is it unusual that it takes about two minutes to process a 100Kb
DocBook document to collect xref targets?  I am using the following
syntax for the Saxon processor.  My computer has 1.6Ghz and 1GB Ram,
Windows XP, Cygwin, and version 1.71.1 stylesheets.

java com.icl.saxon.StyleSheet \
-o dropping~ \
path/to/document/my-document.xml \
xsl-custom-fo.xsl \
collect.xref.targets="only" \
targets.filename="mydoctargets.db"

2. I found that if I add the -o parameter I avoid some odd output in the
terminal.  DocBook XSL, The Complete Guide does not show that parameter
when processing only to generate the targets.  However, if I do not
allow Saxon to create an empty file, I see an XML declaration in the
terminal output:

     Writing mydoctargets.db for book
     <?xml version="1.0" encoding="utf-8"?>

If I do allow Saxon to write the empty file, I see this:

     Writing mydoctargets.db for book

Is the XML declaration in the terminal output harmless or does it
indicate a possible misconfiguration?

Thanks for your help.

Peter Desjardins

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org