Baldur van Lew wrote: > We make extensive use of modular XML in application specific data - files > included using external entities. > > XML-Mind look pretty good at first sight - it handles our external entities > (the module references) correctly but > the problem is with the "module" documents. The modules on their own are > not valid XML (no DTD and entity > definitions are missing) and XML Mind chokes if you try to load one. > > Is there a solution for this? Should we put the .dtd and supporting entity > definitions > in our sub-modules (is this even allowed) of can I stop XML Mind choking on > the > malformed XML?
My answer assumes that your modules don't contain non-well-formed XML (example: a missing '>'). In free Standard Edition, modules included in a master document: * Can have no <!DOCTYPE>. * Can contain references to entities specified in the <!DOCTYPE> of the master document. The main limitation in term of modularisation is: * A module must contain a *single element* and nothing else. Other limitations are described in: http://www.xmlmind.com/xmleditor/_distrib/docs/help/ar01s07s01.html#managedNonmanaged
