Thanks for your inquiry. I have tested the scenario and have managed to reproduce the
same issues at my side. For the sake of correction, I have logged these
problems in our issue tracking system as follow:
SAASWORDS-237 : Paragraph formatting is lost after re-saving Docx SAASWORDS-238 : Watermark (shape node) is lost after re-saving Docx
I
have linked this forum thread to the same issues and you will be
notified via this forum thread once these issues are resolved.
Thanks
for your inquiry. I would like to share with you that issues are
addressed and resolved based on first come first serve basis. Currently,
your issues are pending for analysis and are in the queue. We will update
you via this forum thread once there is any update available on your
issues.
There were two issues SAASWORDS-237 and SAASWORDS-238. SAASWORDS-238 has been fixed in the codebase and expected to be live within this month or start of next month. As far as SAASWORDS-237 is concerned, product team has completed the analysis of this issue and it can take some time because of the complexity of the issue.
We will update you as soon as any ETA is available for this issue.
Unfortunately no ETA for 237 is available yet. ETA request has been forwarded to our product team however as shared earlier, it can take some time because of the complexity. We will update you as soon as we have any update on this.
The issue has been delayed because of its complexity however it has been planned for November release. You can expect this fix to be live on mid of November.
Some part of the issues has been resolved and remaining part is in progress and will be resolved soon. Plan has not been changed and the issue is expected to be fixed in the November release of the codebase.
This fix will be moved to live servers a few days after the release which is expected at the end of this month or start of next month. The original estimate was mid of December and mid of November was shared by mistake.
The root cause of this issue was your document contains HTML Altchunk which was imported incorrectly. There is some difference how MS Word and Aspose.Words import HTML. Our development team is removing these differences and working on making HTML import just like MS Word. This will be a permanent fix to such issues and will take longer period of time.
We had logged an issue to apply a temporary fix for your issue until a permanent fix is available and we were expecting this temporary fix in November. Unfortunately, the temporary fix did not produce the desired results so we did not move that fix to live. Our product team is still working on the issue and it is present in our current month's plans.
A request to share a reliable ETA has been forwarded to our product team and we will update you as soon as we have a concrete date for this fix.
Thanks for being patient. We have good news for you i.e. SAASWORDS-238 have now been resolved. You may now please re-test your scenario with Aspose.Words for Cloud. Hope, this helps.