While using the latest version of Aspose.Words i.e. 16.6.0, we managed to reproduce this issue on our end. We have logged this issue in our bug tracking system. The ID of this issue is WORDSNET-13960. Your thread has also been linked to the appropriate issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.
Thanks for your inquiry. Unfortunately, your issue is not resolved yet. We have asked the ETA of this issue from our product team and will update you as soon as any estimates are available. We apologize for your inconvenience.
This issue has now been resolved and its fix will be available in next monthly release i.e. Aspose.Words 16.8.0. We will inform you via this thread as soon as next release is published.
Thanks for your inquiry. I am afraid, at the moment we don’t have any plans to release interim build such as 16.7.1. However, we will hopefully release 16.8.0 version of Aspose.Words at the start of September 2016.
And, of course, formatting has always to be the same.
Please find attached project and input and output document.
As I already waited long for this fix it will be extremely appreciated if final fix can be provided quickly with 16.8.1 version. Waiting one more month will be really inconvenient.
And, of course, formatting has always to be the same.
Please find attached project and input and output document.
As I already waited long for this fix it will be extremely appreciated if final fix can be provided quickly with 16.8.1 version. Waiting one more month will be really inconvenient.
Thanks in advance,
Oliver
Please follow this thread for further proceedings.