Hi guys,
Hi Hanh,
Thanks for your inquiry. 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-12258. 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 there,
Thanks
for your inquiry. Normally when an issue is reported by a customer it is added to the pool of current issues being worked on by our developers is analysed in a timely manner. However due to the nature of some bugs and the number of features we are working on, this doesn’t always mean we can fix every bug within a short time after it’s reported.
Regarding the ETA of WORDSNET-12258, currently this issue is under analysis phase. Once this issue is analyzed, we will then be able to provide you
an estimate.
Thanks for your patience and understanding.
The issues you have found earlier (filed as WORDSNET-12258) have been fixed in this Aspose.Words for .NET 17.10 update and this Aspose.Words for Java 17.10 update.