It looks like this issue is happening with .doc files too. Can someone check if it’s a known bug or if there’s something wrong with my code that’s affecting the revision info ?
Sample file:
sample_file.zip (37.9 KB)
MS word revision info:
Aspose.words revision info:
@Kldv
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): WORDSNET-27982
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.
@Kldv We have completed analyzing the issue. The problem occurs because MS Word build revisions groups for deleted cells in very strange way. It makes revision group for any row containing deleted cell plus one revision titled “Deleted Cells”. As for formatting revision difference it looks that MS Word ignores SizeBi attribute for paragraph break mark.
We will keep you update and let you know once the issue is resolved.
Thanks for your reply @alexey.noskov, Is there any workaround for this issue until an actual fix is made ?
Hi @alexey.noskov since you identified the issue, I am not fully aware of the internal workings. Could you please categorize the specific changes or types where this issue occurs? For example, is it only related to table cells or other specific change areas? This information will greatly help us narrow down the pain point.
@Kldv As mentioned above, the problem occurs because MS Word build revisions groups for deleted cells in very strange way. It makes revision group for any row containing deleted cell plus one revision titled “Deleted Cells”. As for formatting revision difference it looks that MS Word ignores SizeBi attribute for paragraph break mark.
Thanks for your reply @alexey.noskov, we can see it is showing correct revision info in MS word review section, can we get the same revision info count by calculating programmatically like from meta data etc.
@Kldv The logged defect is exactly about this, i.e. that Aspose.Words incorrectly calculates number of revisions in the document. Unfortunately, we cannot suggest you a programmatic workaround of the issue. So I would suggest you to wait for an actual fix. We will keep you updated and let you know once the issue is resolved.
@alexey.noskov were this working earlier and failed with latest version i.e. v25.2, if yes can you provide version for which it was working
If no could you please prioritise this at earliest because we bought license for Aspose.words for java. we are in the process of getting the license for paid support, we have a release planned in coming days and this is blocker for that release and we are heavily relying on Aspose.words
Hi @Kldv
We are also facing same issue , @alexey.noskov
Could you please ask your team to check on this as our customer uses a lot of docx files with tables and this is giving us very wrong picture in customer front.
@Kldv @abhishek.sonkar We have already completed analyzing the issue, but it is not yet scheduled for development. So we cannot provide you an estimate right now. We will keep you updated and let you know once it is resolved.
Once you get license for paid support, you can escalate the issue in paid support, this will push the issue upper in the queue.
In the following file, I also found that the revision information does not match the Aspose output.
Aspose shows the format changes count as 8, but according to MS Word, it is only 5.
Aspose output docx file:
aspose-output-format-changes.docx (29.2 KB)
@Kldv
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): WORDSNET-28065
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.
Here I am providing more redlined files where we are encountering a count mismatch issue with MS word for revision information (highlighted in bold). As you mentioned in Getting incorrect revision information using Aspose.words Java library - #10 by alexey.noskov it is not only due to the Deleted Cells and SizeBi attribute issue. I found discrepancies in the insertions as well. Could you please review the files mentioned below and let us know what might be causing this issue?
| File Name | Insertions (Aspose/MS word) | Deletions (Aspose/MS word) | Format Changes (Aspose/MS word) |
|---|---|---|---|
| test_127.docx | 04/05 | 02/03 | 06/05 |
| test_128.docx | 02/03 | 01/01 | 00/00 |
| test_129.docx | 01/01 | 01/01 | 24/02 |
| test_132.docx | 00/00 | 00/00 | 02/01 |
| test_134.docx | 18/18 | 04/04 | 43/103 |
| test_135.docx | 17/16 | 06/05 | 04/04 |
| test_136.docx | 15/14 | 06/05 | 04/04 |
| test_140.docx | 02/02 | 03/03 | 06/03 |
| test_142.docx | 18/21 | 25/25 | 1127/1110 |
| test_144.docx | 01/01 | 01/01 | 11/10 |
| test_145.docx | 11/10 | 08/07 | 29/18 |
| test_146.docx | 04/04 | 00/00 | 12/52 |
| test_147.docx | 04/05 | 00/00 | 03/03 |
Aspose-comparison output files listed above
count-mismatch.zip (6.7 MB)
this is the main feature we are offering for our users for the current release, and we are unsure in which scenarios Aspose might produce incorrect results as shown above.
@Kldv
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): WORDSNET-28090, WORDSNET-28091, WORDSNET-28092, WORDSNET-28093, WORDSNET-28094, WORDSNET-28095, WORDSNET-28096, WORDSNET-28097, WORDSNET-28098, WORDSNET-28099, WORDSNET-28100, WORDSNET-28101
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 problem is not reproducible on my side with the latest 25.3 version of Aspose.Words for test_135.docx and test_136.docx documents.
The issues you have found earlier (filed as WORDSNET-28065) have been fixed in this Aspose.Words for .NET 25.5 update also available on NuGet.
The issues you have found earlier (filed as WORDSNET-28099,WORDSNET-28098,WORDSNET-28097,WORDSNET-28096,WORDSNET-28094,WORDSNET-28093) have been fixed in this Aspose.Words for Java 25.5 update.