Converting from Word to PDF using Aspose.Word 14.4.0 Version

Hi Tahir,
I have not yet received any reply from you for our request and, this is really disappointing and annoying.

The request which was raised one year ago is still not addressed completely at your end. This is getting us into a situation where my customers are unhappy and this may sabotage my company reputation.
We do understand that you have lot of request in your queue, but please take this as a priority request from us and give me positive timescale.
We have the following issue reported and still unaddressed by you:

  1. Remove number from TOC

Please get back to us on this required solution or suggest some valid workaround at the earliest.

Thanks
Rajesh

Hi Rajesh,

Thanks for your inquiry. I have asked for the update of WORDSNET-10755 and WORDSNET-10800 from our product team. Both issues are related to WORDSNET-832. As soon as any information is shared by them, I will be more than happy to share that with you. Thanks for your patience.

*rajeshp:

I have not yet received any reply from you for our request and, this is really disappointing and annoying.

The request which was raised one year ago is still not addressed completely at your end. This is getting us into a situation where my customers are unhappy and this may sabotage my company reputation.

We do understand that you have lot of request in your queue, but please take this as a priority request from us and give me positive timescale.

We have the following issue reported and still unaddressed by you:

  1. Remove number from TOC

Please get back to us on this required solution or suggest some valid workaround at the earliest.*

I have checked all these forum threads. All queries were answered by our Aspose staff. Could you please share more detail about this query? We will then provide you information about your query.

Hi Rajesh,

Thanks for your patience. It is
unfortunate that the underlying issue WORDSNET-832 is still unresolved.
Our product team is actively working on this issue however because the
issue is very complex, we won’t be able to commit an ETA at this
time. Hopefully, after the v15.12.0 release, we will be in position to share the ETA.

We apologize for your inconvenience.

Any update on this issue?

Thanks

Hi Rajesh,

Thanks for your inquiry. We have asked from our product team about the ETA of this issue. As soon as any information is shared by them, we will be more than happy to share that with you.

Thank you for your patience and understanding.

Any update on this issue?

Thanks
Rajesh

Hi Rajesh,

Thanks for your inquiry. We do understand your situation, however I am afraid, at the moment we can’t provide you the ETA of this issue. We have spoken to the responsible developer about your issue and regret to share with you that he is unable to commit any ETA at the moment. The MS Word’s logic is not clear for your issue. We will update you via this forum thread once there is any update available on this issue.

We apologize for your inconvenience.

@rajeshp,

Thanks for your patience. It is to inform you that the issue WORDSNET-10755 has been fixed in latest version of Aspose.Words for .NET 18.4. Please use Aspose.Words for .NET 18.4.

The issues you have found earlier (filed as WORDSNET-10755) have been fixed in this Aspose.Words for .NET 18.5 update and this Aspose.Words for Java 18.5 update.