Hi,
I am using GroupDocs.Comparison 18.7.1 Version with .Net. When comparing PDF and DOCX format files, it shows the differences by coloring, but if I compare TXT files, it indicates the changes using () and [] characters instead of coloring. How can I solve this problem?
image.png (7.4 KB)
Could you please share the source and the target files as well? Moreover, we’d recommend you to use the latest API version.
@atir.tahir
Here are the files I compared. You can download from this.
https://portal.synergynow.io/#/_redirect/jwh1N4YTpPfjxYRk22ucRn
@tozer
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): COMPARISONNET-3964
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
@tozer
The latest version of GroupDocs.Comparison for .NET 6 works, but the .NET Framework version gives an error we are unable to fix error because on of the libraries that we are using (Aspose.HTML) is still using System.Text.Encoding.CodePages 4.5.0 and System.Runtime.CompilerServices.Unsafe 6.0.0. So we could suggest you a workaround: just add to your project System.Text.Encoding.CodePages 4.5.0 and System.Runtime.CompilerServices.Unsafe 6.0.0 libraries and then Framework version also will work fine.
Regarding point with highlighting changes with a different color:
For plain text there is no ability to highlight text with a different color. But we could suggest show comparison result as PDF and there we could highlight changes with a different colors. Created follow up task accordingly and will work on it in upcoming release
Ticket ID is COMPARISONNET-4089
@tozer
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): COMPARISONNET-4089
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
The issues you have found earlier (filed as COMPARISONNET-3964) have been fixed in this update. This message was posted using Bugs notification tool by anton.samarskyy
The issues you have found earlier (filed as COMPARISONNET-4089) have been fixed in this update. This message was posted using Bugs notification tool by anton.samarskyy