I tried to import a docx file in Aspose Words Java (see attached) which contains comments with replies & resolved comments but failed to retrieve the information in Aspose.
It seems to me that the replies are converted to regular comments and that the “is resolved” status is simply lost in the process.
Am I missing something or there is indeed no support for advanced features like “comment reply” or “comment resolved” when loading documents in Aspose ?
Thanks for your inquiry. We tested the scenario and have managed to reproduce the same problem on our end. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-14471. Our product team will further look into the details of this problem and we will keep you updated on the status of correction. We apologize for your inconvenience.
EDIT: It looks like this feature has already been implemented in latest versions of Aspose.Words for Java. Please upgrade and confirm. Thanks for your cooperation. https://releases.aspose.com/words/java/
It looks like the following simple code produces the correct results when using the following code with Aspose.Words 16.11.0 (see attachment):
Document doc = new Document("docx_qui_tache.docx");
doc.save("16.11.0.docx");
Can you please upgrade to latest version and see how it goes on your end? If the problem still remains, please create a standalone Java application (source code without compilation errors) that helps us reproduce your problem on our end and attach it here for testing.
I also tried to save the document as html and I couldn’t see anything that could let me differentiate resolved comments & comment replies in the generated html.
Document doc = new Document("docx_qui_tache.docx");
doc.save("16.11.0.html", new HtmlSaveOptions(SaveFormat.HTML));
Thanks for your inquiry. We will do a proper support for advanced Comment handling including extended info access, adding reply to etc. But, we regret to share with you that the implementation of this new feature has been postponed for now. However, the fix of this problem may definitely come onto the product roadmap in the future. Unfortunately, we cannot currently promise a resolution date. We apologize for your inconvenience.