I have a very simple test where I am opening DOCX document and saving it. When I try to open the output document, the document gets corrupted. The document contains section break inside structured document tag.
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. The ID of this issue is WORDSNET-19036. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.
We have good news for you i.e. WORDSNET-19036 has now been resolved. The fix of this issue will be included in the 19.9 (next version) of Aspose.Words. We will inform you via this thread as soon as the next version containing the fix of your issue will be released in next few days.
@awais.hafeez Thank you so much for the update, but this still doesn’t resolve an issue with the section break, I’m trying to load the attached Document using Aspose. Unfortunately, Content Control gets lost.
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. The ID of this issue is WORDSNET-19173. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.
We regret to share with you that the implementation of issue (WORDSNET-19173) has been postponed (no estimate is available at the moment). We will inform you via this thread as soon as this issue is resolved. We apologize for your inconvenience.
Unfortunately, your issue (WORDSNET-19173) is not resolved yet and there is no further news about this issue i.e. the implementation of the fix of this issue has still been postponed. We will keep you posted on any further updates and let you know when this issue will be resolved in future. We apologize for your inconvenience.
I am afraid, WORDSNET-19173 is still not resolved and there is no further news about this issue i.e. the implementation of the fix of this issue has still been postponed. We will inform you via this thread as soon as this issue will be resolved in future. We apologize for your inconvenience.