Compare function generates unnecessary row deletions and inserts when comparing tables

Aspose.Words Product Family
1

Hi,
we have problems with the compare function in Aspose Words for Java. It generates unnecessary and confusing row deletions and inserts.

This is our use case:
We want to create a word document using a table with the left side representing an old version of data and the right side showing changes made in the new version of our data. To achieve that, we create an “old” document with the old version on both sides in this table.
We then compare this document with a “new” document containing the old data on the left side and the new data on the right side in the table. This results in the changes made between the versions to be highlighted on the right side.

This neat trick works great when we try it with Microsoft Word but when we use Aspose we occasionally get highlightings that suggest that a row was removed and directly beneath a new row was added. This is wrong and inconsistent with Word, which correctly recognises, that merely some text changed in this row.

Attached you can find simple example inputs, the output we expect (because it was created with MS Word) and the output Aspose Words creates.

We are able to reproduce this problem with aspose-words-17.11 .
compareTables.zip (105.8 KB)

2

@tobias.hirscher,

Thanks for your inquiry. We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-16282. You will be notified via this forum thread once this issue is resolved. We apologize for your inconvenience.

Please share the Java version that you are using at your end. Thanks for your cooperation.

3

Hi, we use Java 8 in our project.

4

Hello,
I’m working with Tobias and am now handling this issue.

We noticed another bug in our current version of Aspose Words for Java which has already been fixed (Issue with vertical merging in table). We are considering an upgrade in the near future. Can you give us an estimate, whether WORDSNET-16282 will be fixed in a release within a few months? It would greatly help us, because we would solve two issues with only one upgrade.

5

@joachim.schulze,

Thanks for your inquiry. We try our best to deal with every customer request in a timely fashion, we unfortunately cannot guarantee a delivery date to every customer issue. Our developers work on issues on a first come, first served basis. We feel this is the fairest and most appropriate way to satisfy the needs of the majority of our customers.

We have asked for the ETA of this issue from our product team. As soon as any information is shared by them, we will be more than happy to share that with you.

Please note that you reported this issue in free support forum and it will be treated with normal priority. To speed up the progress of issue’s resolution, we suggest you please check our paid support policies from following link.
Paid Support Policies

6

Hello,
are there new information on the ETA?

7

@joachim.schulze,

Regarding WORDSNET-16282, I am afraid, we cannot currently promise a resolution date. Rest assured, we will inform you via this thread as soon as this issue is resolved or any estimates are available. We apologize for your inconvenience.

8

The issues you have found earlier (filed as ) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by MuzammilKhan

9

The issues you have found earlier (filed as WORDSNET-16282) have been fixed in this Aspose.Words for Java 22.3 update.