While using the latest version of Aspose.Words i.e. 13.4.0, I managed to reproduce this issue on my side. I have logged this issue in our bug tracking system. The issue ID is WORDSNET-8215. Your request has also been linked to this issue and you will be notified as soon as it is resolved.
Thanks for your inquiry. Unfortunately, your issue is not resolved yet. The responsible developer has planned to integrate the fix in 13.6.0 release. If everything goes by plan, we are very hopeful to include the fix to your issue in Aspose.Words' June release i.e. 13.6.0. Please note that this estimate is not final at the moment; I will be sure to inform you via this forum thread as soon as your issue is resolved. I apologize for any inconvenience.
Thanks for your inquiry. Unfortunately, your issue is still unresolved. Our development team has completed the analysis of this problem and the root cause has been determined. Currently, your issue is pending for development. We will inform you as soon as this issue is resolved. We apologize for any inconvenience.
PS: The new versions of Aspose.Words for .NET and Java are released at the end of every month and Aspose.Words 13.6.0 will be released around July 1st, 2013.