GroupDocs.Comparison for .NET 19.6 Release Notes
Major Features
Below is the list of most notable changes in release of GroupDocs.Comparison for .NET 19.6:
- Fixed problem when sections moved to the new page
- Fixed typos in API reference
- Implemented sensitivity option
- Implemented calculation coordinates of changes for Words documents
- Fixed content overlapping in resultant PDF documents
- Fixed problem when sections moved to the new page
- Integrated credit based billing system using latest version of Metered
Full List of Issues Covering all Changes in this Release
Key | Summary | Issue Type |
---|---|---|
COMPARISONNET-1846 | Calculate correct coordinates of changes for Words | Improvement |
COMPARISONNET-1929 | Implement sensitivity option | Improvement |
COMPARISONNET-1901 | Integrate latest version of Dynabic.Metered into products | Improvement |
COMPARISONNET-1815 | Ignore comments (for code files mostly) | Improvement |
COMPARISONNET-1816 | Ignore White Space - All, Leading, Trailing, Changes in amount | Improvement |
COMPARISONNET-1813 | Ignore Case - Ignore character case differences | Improvement |
COMPARISONNET-1927 | Merged Document and then document Comparison failed | Bug |
COMPARISONNET-1891 | Text got overlapped with other text or images | Bug |
COMPARISONNET-1930 | Duplicate Images in Result file in PDF | Bug |
COMPARISONNET-1772 | PDF comparison has overlapping and mangled output | Bug |
Public API and Backward Incompatible Changes
Setting Comparison Detail level
- If we set DetailLevel = Middle, we don’t add comment in some document formats (Words, Slides, Cells) if element was added\deleted\modified
- If we set DetailLevel = Middle, we don’t make case insensitive comparison. i.e. M = m.
- Was added sensitivity property. This option defined limit in percents, when element is detected as deleted or inserted.
Minimal value - 0, comparison process not occurs for any length of sequences of two compared objects.
Value by default - 75 comparison occurs when the percentage of deleted or inserted elements in relation to all elements does not exceed 75%
Maximum value - 100. Comparison occurs at any length of a common subsequence of two compared objects..
For instance, we have two words
1)oneSource 2)twoTarget
This two words have very small a common subsequence.Therefore, when comparing them at 70% accuracy, it is not taken into account and we get a completely removed and inserted word:
(twoTarget)[oneSource]
But at 100% accuracy, we take into account this subsequence, despite the fact that it consists of two letters
(tw)o[n](Targ)e[Source](t)
Code snippet:
string source = "source.txt"; string target = "target.txt"; ComparisonSettings settings = new ComparisonSettings(); settings.SensitivityOfComparison = 100; Comparer compare = new Comparer(); ICompareResult result = compare.Compare(source, target, settings);