We tested the scenario and managed to reproduce the same problem on our end. For the sake of correction, we have logged this problem in our issue tracking system. The ID of this issue is WORDSNET-17999. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.
Since this is a critical issue for this, is there any kind of workaround (a different approach to conversion or some changes we can do to the input file) so that we can get pass this issue for the moment?
We have good news for you i.e. WORDSNET-17999 has now been resolved and the fix of this issue will be included in the 19.2 (next version) of Aspose.Words. We will inform you via this thread as soon as the next version containing the fix of your issue will be released at the start of next month.