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-14075. You will be notified via this forum thread once this issue is resolved.
Thanks for your inquiry. The same issue will be fixed in Aspose.Words for .Net and Java.
Please note that the latest version of Aspose.Words for Java is completely auto-ported from .NET, i.e. we do not write code for Aspose.Words for Java; it is generated out automatically from C# code of Aspose.Words for .NET. So there should not be any significant difference in functionalities between Java and .NET versions because the code is mostly the same.
Thanks for your inquiry. Yes, this issue exists in Aspose.Words v16.7.0. We will inform you via this forum thread once this issue is resolved. Thanks for your patience.
Thanks for your inquiry. We regret to share with you that the issue WORDSNET-14075 has been postponed. I am afraid, there is no estimate available at the moment. We will inform you via this forum thread as soon as there are any further developments.