Hi Norm,
wish you all a happy new year! :-)
Am Samstag, 31. Dezember 2011, 07:29:16 schrieb Norman Walsh:
> [...]
> > It seems, it doesn't help to add the Saxon6 jar into the
> > classpath.
> No, it doesn't. I think the only way to fix this would be to write an
> XProc extension step that used the Saxon6 implementation.
Thanks for confirming.
> Or start using the DocBook XSLT 2.0 stylesheets. :-)
Actually I did, but wasn't successfull. :-)
The usual docbook.xsl works like a charm. I don't have any problems with it so
far. However, for some unknown reason, the chunk.xsl doesn't work for me
(yet). I used Saxon9 with the original DocBook XSLT 2.0 stylesheet like this:
$ saxon9 -xi -s:en/xml/DoCookbook.xml \
-xsl:frameworks/db-xslt2/xslt/base/html/chunk.xsl
Interestingly, this doesn't print any "Writing ..." messages. I get these
files now:
chunk-appendix-d62e5692.html chunk-book-d62e2.html
chunk-chapter-d62e2464.html chunk-chapter-d62e475.html
chunk-preface-d62e179.html [...]
Ok, it seems, the naming has been changed, but strangly I didn't get an
index.html file. My naive thought was to have some navigation headers, but
they don't show up in my HTML files. Maybe there is some magic which I've
missed. I would love to use the chunking stylesheet too. :-)
Oh, by the way:
When I've played with the XSLT2 stylesheets, I've came across some bugs. As I
wasn't sure if you prefer still the Sourceforge ticker or Github, I used the
former. Here are some pointers, hope they are helpful:
#3464876 xslt2: keycap/@function not used
#3464633 xslt2: Parameter img.src.path has no effect
#3450421 xslt2: Relative paths for transclusion do not work
#3431422 xslt2: menuchoice is not correctly rendered
> > Has anybody successfully used
> > Calabash with the DocBook XSLT 1.0 stylesheets?
>
> I'll take a quick peek at writing an cx:xslt1 extension step.
Thanks Norman! :-)
--
Gruß/Regards
Thomas Schraitle
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
