We’ve encountered an issue where ink annotations in a docx document seem to vanish when using Aspose.Words (tested 19.1) to convert from DOCX to DOC or RTF format.
The ink annotation shapes do seem to be loaded from the docx document (you can find the shape nodes in the loaded document) and even seem to be present if you reload the converted document, but the content of the ink annotations is missing in the converted version.
Converting the documents using Microsoft Word retains the ink annotations in doc or rtf format.
Is this a bug or are ink annotations not supported for document conversions?
Pen.zip (117.5 KB)
var doc = new Document(@"C:\temp\Ink2.docx");
Node shapes = doc.GetChildNodes(NodeType.Shape, true).ToArray();
foreach (Shape shape in shapes)
We tested the scenario and managed to reproduce the same problems on our end. For the sake of correction, we have logged the following issues in our issue tracking system.
WORDSNET-18108: Ink drawings not preserved during DOCX to DOC or RTF conversion (related to ink1.docx)
WORDSNET-18109: Ink drawings not preserved during DOCX to DOC or RTF conversion (related to ink2.docx)
We will further look into the details of these issues and will keep you updated on the status of corrections. We apologize for your inconvenience.
Do you have any update on when there might be a fix available for these issues?
Thanks for being patient. Regarding WORDSNET-18108, please note that Ink shape is a special shape and contains some metadata within. Please tell what do you actually want? Just visual presentation in output document or output should contain ink metadata as well?
there is value for us in having just the image of the ink annotation show in the converted document. It would be great to have the full data, but happy to have the image conversion done sooner rather than wait longer for the full conversion,
We have logged these details in our issue tracking system and will keep you posted on any further updates.
The issues you have found earlier (filed as WORDSNET-18108) have been fixed in this Aspose.Words for .NET 19.7 update and this Aspose.Words for Java 19.7 update.