Project

Profile

Help

Xinclude problem with docbook document

Added by Anonymous about 18 years ago

Legacy ID: #3914243 Legacy Poster: sh (sh_9109394)

Hallo! I write an manual in docbook xml. For XSLT transformation I use the saxon processor for FO transformation the FOP processor from apache.org. I'm working with WinXP SP2 on Eclipse 3.2 with WTP 1.5 plugin. For the transformations I use an ant script. Now I splitted the chapters af the document (root is 'book') in different files. To join the parts I follow the description in the docbook guide: http://www.sagehill.net/docbookxsl/Xinclude.html#JavaXIncludes But I use Saxon 6.5.5, Xerces 2.8.0 and docbook-XSL 1.70.1. First the transformation worked. But when I use an element '<programlisting></programlisting>' in one chapter I get: [java] Error on line 79 column 20 of file:/L:/workspace/UserManual/docbook/chapter_installation.xml: [java] SXXP0003: Error reported by XML parser: Multiple notations were used which had the name [java] 'linespecific', but which were not determined to be duplicates. [java] Error on line 58 column 91 of file:/L:/workspace/UserManual/docbook/book_user_manual.xml: [java] SXXP0003: Error reported by XML parser: Error attempting to parse XML file [java] (href='chapter_installation.xml'). [java] Transformation failed: Run-time errors were reported [java] Java Result: 2 In the first file there is the '<programlisting>' in line 79, in the second file the 'xi:include' in line 58. First I thought about a xerces problem. But when I only do an XInclude processing with XIncluder and XInclude-ant-task (http://xincluder.sourceforge.net/, http://people.freebsd.org/~znerd/xinclude-task/) it works. And there I use the same Xerces 2.8.0 and JDOM 1.0. Thanks Stefan


Replies (1)

RE: Xinclude problem with docbook document - Added by Anonymous about 18 years ago

Legacy ID: #3914261 Legacy Poster: Michael Kay (mhkay)

As Saxon is trying carefully to point out, the error message comes from the XML parser and not from Saxon itself. If you can establish that Saxon in some way contributes to this problem, then I'll probably need to see the source files to help you. But at the moment, it looks as though Xerces doesn't like your XML, and there's not much I can do about that...

    (1-1/1)

    Please register to reply