@srmbimser
Thanks for your inquiry. We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-17658. You will be notified via this forum thread once this issue is resolved.
We apologize for your inconvenience.
Hi,
Is there an improvement on this issue?
@srmbimser
Thanks for your inquiry. We try our best to deal with every customer request in a timely fashion, we unfortunately cannot guarantee a delivery date to every customer issue. We work on issues on a first come, first served basis. We feel this is the fairest and most appropriate way to satisfy the needs of the majority of our customers.
Currently, your issue is under analysis phase. Once we complete the analysis of your issue, we will then be able to provide you an estimate.
You reported this issue in free support forum and it will be treated with normal priority. To speed up the progress of issue’s resolution, we suggest you please check our paid support policies from following link.
Paid Support Policies
The issues you have found earlier (filed as WORDSNET-17658) have been fixed in this Aspose.Words for .NET 19.3 update and this Aspose.Words for Java 19.3 update.