Table of Contents
DeltaXML DITA Compare Release Notes
- New Feature: Added Arbortext Editor tracked changes output format
- Bug Fix: CALS table overlapping row calculation was taking too long on large tables, this has now been optimised. This was customer support case 270.
- Bug Fix: Fix to ensure that namespaces referenced by processing instructions that mark deletions are correctly serialized in the processing instruction when necessary. This was customer support case 271.
- Bug Fix: Improved the handling of whitespace in deleted markup for the oXygen Tracked Change output format
- Bug Fix: The GUI now uses updated string parameter values correctly. When they are updated, the new value is retained on the comparison configuration dialog.
- Bug Fix: Table cells with row-spans were not being properly grouped; this is now fixed.
- Bug Fix: Added display of XML Processing Instructions and Comments in GUI display pane (in order to display the tracked change output formats)
- New Feature: Added the oXygen Editor/Author tracked change output format.
- New Feature: Added XMetaL Editor tracked change output format
- Enhancement: The re-ordering filter has been enhanced so that elements not mentioned by the ordering specification, comments, and processing instructions are kept in the same relative positions as far as is possible. In particular, comments above an element are kept with that element as it is re-ordered.
- Deprecation: The show-whitespace-changes parameter has been deprecated. Please make use of the new whitespace-processing-mode parameter, see User Guide or API documentation for details.
- Bug Fix: Reduced the amount of extra whitespace added to tables when whitespace changes were requested.
- New Feature: Added a user guide to the release which gives details of how the comparison works and full descriptions of all parameters.
- New Feature: New DITA GUI, making it a lot easier to run your DITA comparisons.
- New release distributions You can now get DeltaXML DITA Compare for Windows, Mac OS X, Java and .NET.
Bug Fix: The matching of specialized data could cause certain outputs to be generated where child elements appear in the wrong order. Code has been order to reorder these children using the appropriate grammar rules. This was customer support cases 239 and 242.
Bug Fix: Certain DITA grammar rules provide for mutually exclusive child elements, for example a taskbody contains either a steps or steps-unordered child. A parameter (steps-conflict-resolution) is provided to control which of these elements is included in the result. This problem has been solved. This was customer support case 242.
- Bug Fix: If the two inputs contained different specializations of the same
topic element e.g.
menucascadeanduicontrolthat, once generalized, match together, there is the potential for the result file to be invalid. This problem has been solved. This was customer support cases 240, 241 and 243.
- New Feature: If the input documents are of differing DITA types, the output document is not re-specialized, it remains as a Topic with class attributes to show specialization details. It is possible to override this behaviour and force specialization using a new parameter. This was customer support case 238.
Bug Fix: Provided values for the
$productNameand$productNameSpacesvariables, which are used in the documentation.Bug Fix: The .NET API sample now references the up-to-date versions of the third-party libraries.
- Enhancement: Comparison of CALS tables has been improved significantly.
- Enhancement: Change to the way that status attributes are added.
status="changed"is now only added to a leaf node (i.e. the deepest node in the XML hierarchy) where a change has occurred rather than at every level of a changed tree. - Incompatible API change: The AttributesWithValue class has been moved into the DITA package (com.deltaxml.dita).
- Incompatible API Change: The
com.deltaxml.config.ConfigPropertiesclass is no longer available. Its functionality should now be accessed usingcom.deltaxml.dita.ConfigProperties. - Licensing: Changes to the licensing mechanism for OEM customers.
- Bug Fix: The input checking no longer requires a space character at the end of a class attribute on the root element.
New Feature: Now uses Saxon 9.3 (Professional Edition).
New Feature: Added functionality that allows arbitrary attributes to be included on added/deleted items. These are placed on the same elements that the 'rev' attributes are added on if they are enabled. N.B. It is left to the user to ensure that the specified attributes are valid in the context where they are added.
Update: Multi-site license type has been replaced by the Team and Bespoke license types.
- First Public Release: First public release of the full DITA comparison tool.