Right, now I've got Saxon 9 in use via Ant.
But ..... I think I've found a blocking issue.
I'm using the DocBook Html-Help stylesheets.
I'm getting the following message from my transform :
[java] Don't know how to chunk with Saxonica
[java] Processing terminated by xsl:message at line 60 in chunker.xsl
[java] Java Result: 1
So.
Can I chunk with Saxon 9 ?
Or does this mean I definitely can't use it and will need Saxon 6 ?
Are the stylesheets written in such a way as to use a Saxon 6 specific facility
while chunking ?
Uncertainly,
Richard.
-----Original Message-----
From: Kerry, Richard [mailto:richard(_dot_)kerry(_at_)atos(_dot_)net]
Sent: 30 January 2013 14:22
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: RE: [xsl] RE: Saxon via Ant - Getting started
That's exactly what I thought. The underlying question was
"how do I get these done via the resolver ?".
Sorry, that got sent before I saw your reply.
I've just tried changing to Saxon 9.
Running from the command line gives trivial looking
differences from the Saxon 6 version :
1. fo:bookmark/@internal-deatination values are different.
I assume that's because of some internal difference in how
they are generated - perhaps based on the time of running.
(also fo:block/@id, fox:destination/@internal-destination and
some others)
2. Saxon 9 generates some empty blocks, ie <fo:block/>,
where Saxon 6 does nothing.
I'm assuming that these are all trivial so will ignore them
unless you want to know more.
Trying putting those values into an ant <java> task seems to
get into Saxon ok.
The previous issue with "-x
org.apache.xml.resolver.tools.ResolvingXMLReader" is because
Saxon 9 needs a colon to separate, not a space, ie
"-x:org.apache.xml.resolver.tools.ResolvingXMLReader".
I now get a "Malformed URL" error. I suspect that is because
I'm using a mixture of "/" and "\" characters. I believe
Java natively wants "/" at all times (and that that is
required by the URL/URI spec) so I'll change everything to
"/" and see how it goes.
Ok - done that. Most of the messages make sense.
I'm still getting a malformed URL - I think it's because it
contains a "..". Which is probably because the batch file I
use to call ant lives in a folder one level down from the
docboook source, so there is a ".." used to get at it.
Note that this works calling Saxon 9 from the command-line
rather than ant.
Appreciatively,
Richard.
Richard Kerry
BNCS Engineer
T: +44 (0)20 82259063
M: +44 (0)7812 325518
Room EBX 301, BBC Television Centre, Wood Lane, London, W12 7RJ
richard(_dot_)kerry(_at_)atos(_dot_)net
uk.atos.net
This e-mail and the documents attached are confidential and
intended solely for the addressee; it may also be privileged.
If you receive this e-mail in error, please notify the sender
immediately and destroy it. As its integrity cannot be
secured on the Internet, the Atos group liability cannot be
triggered for the message content. Although the sender
endeavours to maintain a computer virus-free network, the
sender does not warrant that this transmission is virus-free
and will not be liable for any damages resulting from any
virus transmitted.
________________________________________
From: Michael Kay [mike(_at_)saxonica(_dot_)com]
Sent: 30 January 2013 13:59
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] RE: Saxon via Ant - Getting started
>Where the value of ${xsl_file} is "CustomFo.xsl" and the
path where it
isn't found is actually where the main build.xml file lives.
CustomFo.xsl is elsewhere, its location being in the catalog.
There are
no messages at all containing the word "resolver", so I've no
idea what
ant is doing there.
Ant is effectively trying to get the file itself, rather than asking
Saxon to get it via the resolver.
Michael Kay
Saxonica
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--