Philip,
The extension you're using is meant for the 6.5 line of Saxon Products
which are XSLT 1.0 compliant.
I'd be very surprised if it worked with 9 which is primarily an XSLT 2.0
processory.
To the list,
Have the extensions been ported to Saxon 8/9?
On Fri, Aug 8, 2014 at 7:23 AM,
Hello all,
can anyone confirm whether the Saxon extensions jar (I have tried
saxon65.jar in DocBook XSL 1.78.1) is compatible with Saxon 9HE ?
I just tried it in order to use the colwidth option for tables and got
the error 'No adjustColumnWidths function available', but I think I
have got my
Hi all,
I'm trying to build XHTML5 output through the DocBook 1.78.1 XSL
stylesheets. My transformation is being invoked via Calabash XProc.
I can successfully invoke 'docbook/xhtml5/docbook.xsl' to create
(non-chunked) XHTML5 output with tools like xsltproc, but Calabash gives
the following
Just putting together a new DocBook system using Saxon.
Using Docbook 5. (5.1 still looks to be beta)
Should I be using Saxon 6 or 9 ?
And if 6 I note that there are some extensions available. In that case do I
just need what's in extensions (ie extensions/saxon65.jar) or should I use
, 2012 4:43 AM
Subject: [docbook-apps] Saxon 6 or 9 ? And extensions - extensions/saxon65 or
use docbook-xsl-saxon
Just putting together a new DocBook system using Saxon.
Using Docbook 5. (5.1 still looks to be beta)
Should I be using Saxon 6 or 9 ?
And if 6 I note
Just putting together a new DocBook system using Saxon.
Using Docbook 5. (5.1 still looks to be beta)
Should I be using Saxon 6 or 9 ?
And if 6 I note that there are some extensions available. In that case do I
just need what's in extensions (ie extensions/saxon65.jar) or should I use
Good morning:
Has anyone tried using the new Saxon CE to run transformations in the
browser? Did it work for you? Did you have to make any changes to your
customization layers if it did work?
Carlos
-
To unsubscribe, e-mail:
| -Original Message-
| From: Dick Hamilton
|
| So, the question is, should the extension treat a final newline this
| way?
|
| I'm inclined to think that it should not do this. It's not a
| big deal if
| your content is inline, but with xi:include, it means you need to
|
Dick Hamilton wrote:
So, the question is, should the extension treat a final newline this
way?
I'm inclined to think that it should not do this. It's not a big deal if
your content is inline, but with xi:include, it means you need to
manipulate your file to remove the newline character,
I'm running into something that might or might not be considered a bug
in the way the Saxon linenumbering extension works.
Here's the setup:
- I'm using Saxon and the latest stylesheets
- The parameters are set up for line numbering
(linenumbering.everyNth=1, use.extensions=1, and
On Thu, Mar 18, 2010 at 6:07 PM, Mauritz Jeanson m...@johanneberg.com wrote:
| -Original Message-
| From: Mathieu Malaterre
|
| ...
| Failed to interpret image: Sketches/Site.svg
| ...
|
| I looked at the output using firefox and everything seems ok. Am I
| missing
Hi there,
I recently switch from xsltproc to using saxon (I wanted syntax
highlighting). However after the switch saxon keeps complaining about:
...
Failed to interpret image: Sketches/Site.svg
...
I looked at the output using firefox and everything seems ok. Am I
missing something ? Is
| -Original Message-
| From: Mathieu Malaterre
|
| ...
| Failed to interpret image: Sketches/Site.svg
| ...
|
|I looked at the output using firefox and everything seems ok. Am I
| missing something ? Is there an option to remove this warning ?
The warning comes from the
Hi there,
I am trying to understand what so different in how catalog are
handled in between xsltproc and saxon (I need to be able to use one or
the other). Basically is the following legal:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE article PUBLIC -//OASIS//DTD DocBook XML V4.5//EN
On Wed, Mar 17, 2010 at 9:30 AM, Mathieu Malaterre
mathieu.malate...@gmail.com wrote:
I cannot make it work using saxon 6.5.5 on a debian machine. It fails with:
java -cp
On Wed, Mar 17, 2010 at 5:40 PM, Keith Fahlgren abdela...@gmail.com wrote:
On Wed, Mar 17, 2010 at 9:30 AM, Mathieu Malaterre
mathieu.malate...@gmail.com wrote:
I cannot make it work using saxon 6.5.5 on a debian machine. It fails with:
java -cp
On Wed, Mar 17, 2010 at 5:54 PM, Keith Fahlgren abdela...@gmail.com wrote:
On Wed, Mar 17, 2010 at 9:45 AM, Mathieu Malaterre
mathieu.malate...@gmail.com wrote:
I believe the file is loaded properly, except the matching does not
work in one case. Here is the output when I set verbosity:
#
I can't, for the life of me, get saxon to output anywhere but the local
directory. Reading the docs, I found three different params for
specifying the output directory, none of which work.
The -o method, (from the saxon usage prompt), which it ignores:
java -cp
| -Original Message-
| From: Mike
|
| I can't, for the life of me, get saxon to output anywhere
| but the local
| directory. Reading the docs, I found three different params for
| specifying the output directory, none of which work.
You are probably looking for the base.dir
Mauritz Jeanson wrote:
| -Original Message-
| From: Mike
|
| I can't, for the life of me, get saxon to output anywhere
| but the local
| directory. Reading the docs, I found three different params for
| specifying the output directory, none of which work.
You are
| -Original Message-
| From: Mike
|
| You are probably looking for the base.dir parameter:
|
| http://docbook.sourceforge.net/release/xsl/current/doc/html/b
| ase.dir.html
|
| It seems as if you might be confusing regular chunked
| output and Website
| output. They
Hi,
I'm trying to use a XSLT 2.0 to translate C# XML to DocBook XML. I use a
Saxon processor and it doesn't seem to recognize the XSLT
xsl:result-document Does any one know why this is happening?
Lillian Sullam
-Original Message-
From: Lillian Sullam
I'm trying to use a XSLT 2.0 to translate C# XML to DocBook
XML. I use a Saxon processor and it doesn't seem to
recognize the XSLT xsl:result-document Does any one know
why this is happening?
The subject line says Saxon 9. Are you
Jeff Powanda wrote:
OK, I guess I was wrong to say that Xerces completely supports XInclude.
I'm using Saxon 6.5.3 with Xerces 2.7.0 and it handles xi:include with xpointer fine when I use shorthand pointers to a DTD-determined ID.
I stand corrected Jeff.
I'll add it to the faq.
regards
Hi all,
funny I'm struggling with similar issue.
I did set up saxon to use Xerces 2.9.0 and while full inclusions like
xi:include href=Inserted.xml/
works, referencing an id with
xi:include href=Inserted.xml xpointer=para/
doesn't work:
Camille Bégnis wrote:
Hi all,
funny I'm struggling with similar issue.
I did set up saxon to use Xerces 2.9.0 and while full inclusions like
xi:include href=Inserted.xml/
works, referencing an id with
xi:include href=Inserted.xml xpointer=para/
doesn't work:
---
I
Dear Camille,
I reported the problem on Xerces Jira some time ago, see it logged here:
https://issues.apache.org/jira/browse/XERCESJ-1113
I provided also a patch in the above report that works around the
problem (and that we use in oXygen to make that work).
Best Regards,
George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks Dave and George,
so is there another parser that would support this (without applying a
patch), and how to use it with saxon?
Thanks,
Camille.
Dave Pawson a écrit :
Camille Bégnis wrote:
Hi all,
funny I'm struggling with similar issue.
: Tuesday, June 12, 2007 5:19 AM
To: Camille Bégnis
Cc: apps docbook
Subject: Re: [docbook-apps] saxon, xerces, xinclude, and DB5 (was Re:
[docbook-apps] trouble using FOP to process FO file generated by Xalan or Saxon)
Camille Bégnis wrote:
Hi all,
funny I'm struggling with similar issue.
I
2007/5/1, Mauritz Jeanson [EMAIL PROTECTED]:
Don't use the -jar option. Either set the CLASSPATH environment variable (to
contain both saxon.jar and saxon65.jar), or use the -classpath option. In
both cases, supply the full name of the main class, as in your first command
line example above.
Hi,
I have done searches and already read
http://www.oasis-open.org/archives/docbook-apps/200406/msg00101.html.
However in my case linenumbering does not work, despite saxon
extension. I know saxon extension works because I use it to add
callouts and callouts need it. Here is what is working
-Original Message-
From: Thierry Bothorel
Uhm, here is the otput (never used like that) :
java com.icl.saxon.StyleSheet linenumbering.xml
~/local/lib/docbook-xsl-1.72.0/xhtml/docbook.xsl use.extensions=1
linenumbering.extension=1 linenumbering.html
Exception in thread main
Robert P. J. Day wrote:
based on the answer to my last email, i'm going to stick
with saxon 6.5.2 for my work. however, i went looking for
an RPM that would be compatible with RH 8.0, and all i could
find at www.rpmfind.net were mandrake cooker RPMs, which
won't install as they have a
. I've fixed the source, and everything works just fine.
Jeff Beal
-Original Message-
From: Daniel Veillard [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 5:47 PM
To: Jeff Beal
Cc: DocBook Mailing List (E-mail)
Subject: Re: DOCBOOK-APPS: Saxon crashing: java.lang.StackOverflowError
On Friday, Saxon suddenly began crashing with a
java.lang.StackOverflowError. I've been using the configuration I have
now for at least six months, with no such problem. I've been looking
through CVS at the source changes we made, and the only significant change I
can find is that I went through
On Tue, Jan 14, 2003 at 04:42:51PM -0500, Jeff Beal wrote:
hard-coded ulink/s into link/s. (By 'a bunch' I mean 15,000.) XSLTProc
was also crashing after the change. Can anybody think of any reason why
Hum ... how ?
some guidelines at
http://xmlsoft.org/XSLT/bugs.html
Capturing the
Title: saxon how to?
Running saxon from command line results in:
java -jar /usr/share/sgml/docbook-xsl-1.50.0/extensions/saxon65.jar
Failed to load Main-Class manifest attribute from
/usr/share/sgml/docbook-xsl-1.50.0/extensions/saxon65.jar
Is this actually the way to use saxon? Am I
Pfistner, Norbert wrote:
Running saxon from command line results in:
java -jar /usr/share/sgml/docbook-xsl-1.50.0/extensions/saxon65.jar
Failed to load Main-Class manifest attribute from
/usr/share/sgml/docbook-xsl-1.50.0/extensions/saxon65.jar
This is not JAR archive of Saxon. This JAR
* Pfistner, Norbert; [EMAIL PROTECTED] on 24 May, 2002 wrote:
/usr/share/sgml/docbook-xsl-1.50.0/extensions/saxon65.jar
Is this actually the way to use saxon? Am I missing something?
I have jdk1.3 installed on a linux (suse7.2) machine.
java -version verifys this.
How do I get saxon running?
Steinar Bang [EMAIL PROTECTED]:
Steinar Bang [EMAIL PROTECTED]:
Platform: Intel PIII, RedHat 7.2, JDK 1.3.1, Saxon 6.5-1mdk (from the
Mandrake Cooker distribution), DocBook 4.1.2, DocBook-XSL 1.48
(example files attached at the end)
[snip!]
When I do this, I get error messages both when
I did a quic experiment with Saxon 6.5 and it looks like the extension API
is unchanged. The next XSL stylesheet release will include a saxon65.jar.
Until then, just use the saxon644.jar.
Be seeing you,
norm
--
From: Gershon L Joseph [EMAIL PROTECTED]
Thanks, that solves the problem. I forgot I had removed the file:// part
of the URL for Omnimark. Now I get the following error:
Error on line 7 of
file:/C:\tools\docbook\docbook-xsl-1.45\htmlhelp\htmlhelp.xsl
:
java.io.FileNotFoundException:
/ Dave Pawson [EMAIL PROTECTED] was heard to say:
| At 08:08 PM 7/7/01, Norman Walsh wrote:
| I am relieved to report that Saxon 6.4.2 fixes the
| xsl:include/xsl:import problem.
|
| Confirmation please,
| will that remove the need to use extensions for 'anything' in the xsl stylesheets?
| E.g.
I am relieved to report that Saxon 6.4.2 fixes the
xsl:include/xsl:import problem.
The xsl:include/xsl:import bug is so serious and difficult to detect
that I plan to remove all support for earlier Saxon releases from the
next XSL Stylesheet release.
This won't actually prevent anyone from
At 08:08 PM 7/7/01, Norman Walsh wrote:
I am relieved to report that Saxon 6.4.2 fixes the
xsl:include/xsl:import problem.
Confirmation please,
will that remove the need to use extensions for 'anything' in the xsl stylesheets?
E.g. the unicode callout numbers?
Regards DaveP
Hi,
I have a weird problem. Using same stylesheets (1.40), xalan 1.2.2
creates tocs for chapters and sections properly while saxon (6.2.2 6.3)
completely skips them. Saxon transforms everything else properly.
Anyone else experiencing this?
Thanks,
Vladimir
/ Vladimir Blagojevic [EMAIL PROTECTED] was heard to say:
| I have a weird problem. Using same stylesheets (1.40), xalan 1.2.2
| creates tocs for chapters and sections properly while saxon (6.2.2 6.3)
| completely skips them. Saxon transforms everything else properly.
|
| Anyone else
Hello
At 08:59 PM 5/25/01, Kunath, Marcel wrote:
I was trying out an example but it gave me this error:
F:\saxon\samplesjava com.icl.saxon.StyleSheet data\othello.xml
styles\play.xsl
dir=playhtml
Exception in thread main java.lang.NoClassDefFoundError:
com/icl/saxon/StyleSheet
It
On Fri, May 25, 2001 at 03:59:22PM -0400, Kunath, Marcel wrote:
I was trying out an example but it gave me this error:
F:\saxon\samplesjava com.icl.saxon.StyleSheet data\othello.xml
styles\play.xsl
dir=playhtml
Exception in thread main java.lang.NoClassDefFoundError:
At 08:59 PM 5/25/01, Kunath, Marcel wrote:
I was trying out an example but it gave me this error:
F:\saxon\samplesjava com.icl.saxon.StyleSheet data\othello.xml
styles\play.xsl
dir=playhtml
Exception in thread main java.lang.NoClassDefFoundError:
com/icl/saxon/StyleSheet
It says to add the
Before anyone else notices, I'll report the bug: the XSL stylesheets
don't work with Saxon 6.3. Mike has fiddled with all the interfaces
again, sigh. I'll get to it eventually...
Be seeing you,
norm
--
Norman
51 matches
Mail list logo
