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

Free Support Forum - aspose.com

Wrong indents of list after comparing

Aspose.Words Product Family
#1

After document comparing the indents of a numbered list are disappeared.
original (2.2 KB)
edited.png (7.5 KB)
compared.png (6.5 KB)

Test code:

License license = new License(); license.setLicense(ListCompareBug.class.getClassLoader().getResourceAsStream("Aspose.Words.lic")); Document original = new Document(new FileInputStream("./original_document.docx")); Document edited = new Document(new FileInputStream("./edited_document.docx")); original.compare(edited, "John Doe", new Date()); original.save("compared_document.docx", SaveFormat.DOCX);

#2

@Rodion

Thanks for your inquiry. Please ZIP and attach your input Word documents here for testing. We will investigate the issue on our side and provide you more information.

#3

I’ve attached the documents and a snippet to reproduce. I used Aspose version 18.11.wrongListIndetsAfterComparing.zip (17.6 KB)

#4

@Rodion

Thanks for your inquiry. We have tested the scenario using the latest version of Aspose.Words for Java 18.12 and have not found the shared issue. So, please use Aspose.Words for Java 18.12.

We have noticed that the space between list number and its text is increased in output document. Please check the attached image for detail. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-17971. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

#5

It looks like Microsoft Word and LibreOffice render the document differently. Actually it doesn’t depend on a version of Aspose.
But we still have an issue because after comparing we convert the document to HTML. And the numbered list isn’t converted correctly. Screenshot from 2018-12-25 10-25-34.png (4.2 KB)
I’ve attached a new snippet.
wrongListIndentAfterComparingAndConvertingToHtml.zip (17.6 KB)

#6

@Rodion

Thanks for your inquiry.

Yes, your understanding is correct.

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

We apologize for your inconvenience.

#7

The issues you have found earlier (filed as WORDSNET-17972) have been fixed in this Aspose.Words for .NET 19.3 update and this Aspose.Words for Java 19.3 update.

#8

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