-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Michael, Thanks for the information. This is a very interesting tool and I think it will be useful for many people. I've put follow-up questions inline below.
Currently entities are only preserved in the general XML comparison mode (which produces oXygen tracked changes). This default behavior can be configured by changing the value of the 'Preservation Mode' parameter. Note that the general XML comparison mode's configuration parameters are made available by pressing the 'Configure' button on the Comparison file/window selection panel.
The DITA and DocBook comparison modes always expand entity references, as their revision flag markup is not intended for round-trip processing.
I'm not seeing a "Preservation Mode" field in the "Preferences for Compare DocBook" window.
The DocBook specific comparison mode, by default, expands xi:includes elements. This can be turned off by 'unchecking' the 'Enable XInclude' parameter. The general XML and DITA comparison modes do not expand xi:include elements.
I see. I guess it would be quite a complex process to compare two files and their xincluded contents while preserving the xincludes. The tool would have to name and save new versions of all the xincluded files in a new directory and update all the hrefs on the xinclude elements. I could imagine situations that would be hard to process (say if an element were moved from the main file to an xincluded file with no other changes). But for a more limited case, say where all the xincluded files are code listings, this could work.
2. If you have a document with a DOCTYPE statement but with no DTD, it fails to parse the document. This situation arises when you use a schema to validate the document but add a DOCTYPE to declare entities. For example, if you attempt to load two versions of the following valid DocBook 5.x document, it fails to load the first one complaining that "book" has not been defined:
We will address this bug, which arises due to the inappropriate use of DTD validation. One work-around is to compare these documents by turning off the 'Validation' configuration parameter. Alternatively, the general XML comparison successfully compares these files.
Ok, thanks. Turning off validation works around the issue for now. David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOFc34AAoJEMHeSXG7afUhyT0H/21R8Qp+4jeExaQ4gqCCQF8/ Z9uvB2KeQsdvPhrVQB8beC0eyAAvataJjZVRyN7fsqsW6/SUV9zKF6FAuzwDOwVj IwzgZm/9OXE61dIT6bEKQyMvCxxme1rwdA0sn08Mbtzbt/FwwJesgniKYV2JeTPQ tr/pVswiHlH3NRtddBJRumHm63GiWZ77vM/Y0lvdetAV4M9qCMlq3awO6aP3PJGl UpGNLw7o+ULeyQ+ecx8GibivgCrVB41tprbsetZcfLz6fh0TcLVTvBHVIyqlOnpv kUgUyG7Ir58ZK3IYN+gEBRGiMEcGj2GPzjVDPZ5bGEdllDoXhAgwSXScNSaglgY= =UI0I -----END PGP SIGNATURE-----
