Hi there,
Hi Scherge,
Thanks for your inquiry. It would be great if you please share following detail for investigation purposes.
- Please attach your input Word document.
- Please
create a standalone/runnable simple Java application that demonstrates the code (Aspose.Words code) you used to generate
your output document - Please attach the output Word file that shows the undesired behavior.
- Please
attach your target Word document showing the desired behavior. You can
use Microsoft Word to create your target Word document. I will
investigate as to how you are expecting your final document be generated
like.
it is difficult to say what the problem is without the Document(s) and
simplified application. We need your Document(s) and simple project to
reproduce the problem. As soon as you get these pieces of information to
us we’ll start our investigation into your issue.
Hello Tahir,
Hi Scherge,
Thanks for sharing the detail. I have tested the scenario and have managed to reproduce the same issue at my side. For the sake of correction, I have logged this problem in our issue tracking system as WORDSNET-11344. I have linked this forum thread to the same issue and you will be notified via this forum thread once this issue is resolved.
We apologize for your inconvenience.
Hi Tahir,
Hi Scherge,
Thanks for your patience. The
issue WORDSNET-11344 has been resolved and its fix will be available in
Aspose.Words v15.2.0. Hopefully, next version of Aspose.Words will be available in next week. We will inform you via this forum thread as soon as the
this release is published.
Thanks for your patience.
The issues you have found earlier (filed as WORDSNET-11344) have been fixed in this .NET update and this Java update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.