UpdateFields produces TOC that is different to Word

Aspose.Words Product Family
1

Hello,

We have found a custom TOC field producing a very different result when updated via Aspose.Words 15.12.0 compared to Word. This uses a /t option with a value that ends in comma, which I accept is odd but nonetheless would like it behave the same as Word.

Thanks,

Ted

2

Hi Ted,


Thanks for your inquiry.

While using the latest version of Aspose.Words i.e. 15.12.0, we managed to reproduce this issue on our end. We have logged this issue in our bug tracking system. The ID of this issue is WORDSNET-12905. Your thread has also been linked to this issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.

Best regards,
3

The issues you have found earlier (filed as WORDSNET-12905) have been fixed in this .NET update and this Java update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.