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

Free Support Forum - aspose.com

DOCX accepting all revisions leaves Fallback texts unchanged

Hi Aspose team,

We encountered the following problem:


When we try to accept all revisions in the attached docx and resave it, some change-tracked content still stays in the document.
Actually, the Fallback part of the AlternateContent is not accepted at all, only the text under Choice.
So if we open the document in an older version of Word, the content is still change-tracked.
Our goal would be to remove every change-tracked content from the document, and there shouldn’t be any sign of track changes if we accept all of the revisions.

Please let us know if we can provide any more details to help you investigate the issue.

Best regards,

Gergely Vándor
Hi Gergely,

Thanks for your inquiry. We have not found any revisions in output document when it is opened in MS Word 2013 and 2016. Could you please share which older version of MS Word you are using to check revisions? We will then investigate this issue further and provide you more information on this.

Well, we tried it out and MS Word 2007 shows those revisions.
As far as I know the Fallback tag inside an AlternateContent represents the content for Word 2007 and older versions, and unfortunately we have to support those old versions because of our customers.

Please let us know if we can provide any more details to help you investigate the issue.

Best regards,

Gergely Vándor
Hi Gergely,

Thanks for sharing the detail. 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-14692. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

@gergelyv,

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

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