docbook-apps

  • 1.  [docbook-apps] TextFactory import failing under Saxon 9.1

    Posted 03-30-2009 15:56
      |   view attached

    I'm not sure if I should be posting this to the Saxon list as well.

    Let me know what you think.

    docbook-xsl-1.74.3/fo/graphics.xsl

    xmlns:stext="http://nwalsh.com/xslt/ext/com.nwalsh.saxon.TextFactory"

    Results in:
    java.lang.ClassCastException: com.nwalsh.saxon.TextFactory

    Full error message attached.

    Using:
    docbook-xsl-1.74.3/fo
    Saxon 9.1
    Same results under Saxon 8.8


    ~Shane Handford

    Attachment(s)

    txt
    TextFactory_DBK_test.txt   3 KB 1 version


  • 2.  RE: [docbook-apps] TextFactory import failing under Saxon 9.1

    Posted 04-05-2009 09:26
    |


  • 3.  Re: [docbook-apps] TextFactory import failing under Saxon 9.1

    Posted 04-07-2009 17:18

    Thanks, that's what I thought.

    We're not switching back to Saxon 6. Using XSLT2 And the error handling
    / validation is far superior in Saxon 9.

    We've had to comment out the use of TextFactory from our Docbook XSL source.

    How will this be handled when Docbook releases an XSLT2 version?

    Thanks,
    Shane


    Mauritz Jeanson wrote:
    > |


  • 4.  RE: [docbook-apps] TextFactory import failing under Saxon 9.1

    Posted 04-07-2009 18:47
    |


  • 5.  Re: [docbook-apps] TextFactory import failing under Saxon 9.1

    Posted 04-07-2009 18:59

    The project I work on has an extensive customization layer on top of
    Docbook XSL.

    The customization layer I work with was written by multiple developers
    in a big hurry. This was all done in XSLT 1.0. It's a mess.

    We're in the process of re-writing / cleaning up our customization layer.

    The error handling in Saxon 9 is less forgiving than Saxon 6 and forces
    us to write better code through more extensive error reporting. S9
    halts processing on stylesheet issues that S6 would overlook. Example:
    string / integer comparison (casting).

    I like having the ability to use XSLT 2.0 in that customization layer.
    There's a lot more that XSLT 2.0 offers me and the other developers I
    work with.

    ~Shane

    Mauritz Jeanson wrote:
    > |