Free Support Forum -

Convert / Re-save Microsoft DOC to DOCX with Aspose.Words REST API issue


We used Aspose cloud convert to convert word file to Docx.
We get some issues with that:
  1. Space in table after convert is too big
  2. Space between bullets too, get big after convert
  3. Watermark disappears
  4. Paragraph “Spacing after” and “Line spacing” changed (line spacing change to Multiple)

Attached are:
  • Image with problems 1-4
  • The “original” word document before Aspose convert (“No_Aspose_Convert…docx”)
  • The word document after Aspose convert (“Aspose_Convert…docx”)

Hi Alon,

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

have linked this forum thread to the same issues and you will be
notified via this forum thread once these issues are resolved.

We apologize for your inconvenience.


Can you please update us about the bugs above?

Hi Alon,

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.

Thank you for your patience and understanding.

This bug was opened a over a month ago and we still haven’t got any update status.

Hi Alon,

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.

Best Regards,

Thanks for the update.

Any update regarding SAASWORDS-238?

Hi Alon,

It has been fixed. Please check at your end and let us know if it is fixed at your end also.

Best Regards,

Yes, thanks.

Any progress on 237?

Hi Alon,

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.

Sorry for the inconvenience.

Best Regards,

Any update on 237?

This bug is open for three months without any response.

This is really damaging our service as we rely on Aspose cloud to create documents.

What is the escalation procedure?

Hi Alon,

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.

We are sorry for the inconvenience.

Best Regards,


Do you a date for the November update?

Hi Alon,

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.

Sorry for the confusion.

Best Regards,

Do you have a release date for this fix?

This is a major issue and is open for more than 5 months now.

Hi Alon,

We are extremely sorry for the delay.

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.

Best Regards,

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.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.

SAASWORDS-238 was resolved about two months ago.

What about SAASWORDS-237?

Hi Alon,

The issue is in progress. We will update you as soon as it is resolved. Sorry for the inconvenience.

Best Regards,