We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Document.Compare generates the incorrect output using Java

Using aspose-words 18.5 for Java.

Comparing the v1 & v2 documents attached, we’ve inserted ‘child’ bulleted items in the item 1.10.
The aspose words generated comparison flags a revision for all subsequent numbered items (see “insert-with-outline-numbering-and-bullets-aspose-comparison.docx”)

image.png (25.0 KB)

Native word compare gives just the child bulleted items as inserted (see “insert-with-outline-numbering-and-bullets-native-word-comparison.docx”)

image.png (19.2 KB)

Is this a known issue? Is there anything that can be done in compare options to adjust the behaviour?

thanks,
Kevin

insert-with-outline-numbering-and-bullets.zip (368.3 KB)

1 Like

@kevinjansz

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-20945 . You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

Thank you for confirming.

Could I ask what would be a approximate turn-around on issues such as this?
Is it: too early to say; likely to be in next point release; unlikely to be in any release this year?

Whatever information we can get - however rough - would be valuable for planning what we do on our side (for example looking into work-arounds) and communicating with stakeholders.

@kevinjansz

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. We 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.

Currently, your issue is pending for analysis and is in the queue. Once we complete the analysis of your issue, we will then be able to provide you an estimate.

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