bomots-Verlag wrote: > > > thank you very much for your answer. > >> For a real diagnostic, I need to get a hand on the document your are >> trying to export. >> > Here comes the document. Again thank you very much for your support. >
--> The diagnostic is pretty simple: * Your document starts with: --- <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "../../struktur/DocBook/docbookx.dtd" [ <!-- source in the book content and other entities --> <!ENTITY % content SYSTEM "entities/content.ent"> %content; ]> --- * In order to ``export'' your document to other formats, XMLmind XML Editor creates a flattened copy of your document (__doc.xml) in a temporary directory. All the graphics files are copied along with the document. The problem comes from the fact that XMLmind XML Editor does not also copy "entities/content.ent" (unlike graphics files, entities are not considered to be resources of the document). * Therefore, Saxon, the XSLT engine, which is the first step of the export, fails to read __doc.xml. --> In summary, if you intend to work with modular documents built using the references to external entities mechanism, we recommend to choose another XML editor (no offense intended). XMLmind XML Editor has not been designed to be good with this legacy technology. We do not intend to remove this limitation. XMLmind XML Editor v4, which should be released next week, is even worse than v3 at dealing with references to entities. On the other hand, XMLmind XML Editor v4 is pretty competent for more structured modularization mechanisms: conref for DITA documents, XInclude for DocBook, XHTML, etc.
