Release 8.0.2 - 4th August 2020
XML Merge no longer throws an exception during table processing.
Release 8.0.1 - 5th June 2020
XML Merge now correctly resolves the merge result based on version priority.
Release 8.0.0 - 30th March 2020
Created a new package, com.deltaxml.merge.config, that now contains enumerations and configuration classes.
Removed some of the static HTML documentation that was previously moved to our website. Removed release notes file from the release, this is now available on our documentation site (that you are reading right now!) Previous release notes are available here: Pre-8.0.0 Archive
HTML table processing in XML Merge has been updated to identify invalid tables. Merge objects can now be configured to handle the invalid tables and add useful warnings or throw an exception.
HTML tables which are semantically the same but are different in terms of <col> and <colgroup> are now normalised to produce a better result.
Where HTML tables in the input documents have a different <tbody> element-count, but the same contents, the difference may be ignored.The merge now handles the case when the colspan in a CALS table only exists in one of the input files.
CALS table processing has been modified to avoid duplicating the table when a new column is added or deleted within an existing column span.
When a CALS table row is added within an existing row-span section, the merge result shows only the new row marked up, without duplicating surrounding rows.
XML Merge now generates useful error messages when CALS table's spanning, overlapping or colnum attributes have incorrect value types.
For a CALS table with added/deleted columns, the alignment of entry elements referencing colspec elements in a CALS table has been improved.
XML Merge no longer throws an exception if a row spanning value is not an integer. This case is now handled properly by the table checker.
Fixed a bug in Sequential Merge when using ‘orderless’ processing where subsequent versions added, deleted, and re-added identical elements. We consider these changes to be separate edits and should not match together, so the delta has been fixed and identical elements added in alternating versions will no longer match together. This has always been the case with ordered merges, but there was a bug with ‘orderless’ merges.
Fixed a bug in Concurrent Merge where an attribute not present in the base is added to edits - produced an incorrect delta.
Fixed a bug in Sequential Merge in <deltaxml:textGroup>s where identical text in subsequent versions was not grouped together in the same <deltaxml:text>.