BUG in Aspose.Document docx format when using track changes

Aspose.Words Product Family
1

Until this bug is fixed people cannot trust using Aspose with document that have track changes enabled!
If a document (docx) has track changes enabled and a user has moved a section in the document and thus generated a moved tracked change then Aspose does not correctly understand the change and generates a garbled document when saving.
To reproduce this bug do the following to the attached document:

var document = new Document("file");
document.Save("outfile");

Open the two documents and compare the result to see that they are different.
Basically what happens is that Aspose correctly copies the line to the top of the document but does not remove it from where it was before. Therefore the line is there twice.
We are using v9.1 of Aspose.Words.
This is actually a major problem for us since we are working on a customer project with a deadline coming up. If the bug is not fixed quickly or a suitable work around is found we might have to switch component and stop using Aspose.

2

Hello

Thank you for reporting this problem to us. I managed to reproduce the problem on my side. Your request has been linked to the appropriate issue. You will be notified as soon as it is fixed.
Best regards,

3

Hello
When do you expect to have a fix this error? We are in big need of a fix for this issue, for an important customer. We have built the entire Word logic with Aspose, and would hate to replace that.
If there is a workaround please do tell, then we can use that for now…
I’m looking forward to hearing from you.

4

Hello

Thanks for your inquiry. Unfortunately, the issue is still unresolved and currently I cannot provide you any reliable estimate regarding this issue. You will be notified as soon as it is fixed.
Best regards,

5

This is a move revision. Aspose.Words does not support move revisions yet in codecs and in the model.
Aspose.Words supports the following revisions:

  • insert
  • delete
  • list numbering
  • formatting

The example that you’ve attached actually seems to occur pretty rarely. Most move revisions wrap insert and delete revisions inside them and processing such documents in Aspose.Words looses the info about that the text was moved, but the inserted/deleted text appears correctly.
Sorry it causes a trouble in your case. But I have postponed implementation of move revisions until later.