Hi,
Hi Wahaj,
Thanks for your inquiry. I have tested the scenario and have managed to reproduce the same issue at my side. For the sake of correction, I have logged this problem in our issue tracking system as WORDSNET-11310 and WORDSJAVA-991. This issue is related to both Aspose.Words for Java and .NET. I have linked this forum thread to the same issues and you will be notified via this forum thread once these issue are resolved.
We apologize for your inconvenience.
Hi Aspose Support,
Hi Wahaj,
Thanks for your inquiry. I would like to share with you that issues
are addressed and resolved based on first come first serve
basis. Currently, your issue is pending for analysis and is in the queue. I am afraid, we can’t provide you any reliable estimate at the
moment. Once your issue is analyzed, we will then be able to provide you
an estimate.
Thanks for your patience and understanding.
Hi Wahaj,
Thanks for your inquiry. I have verified the status of both issues from our issue tracking system. The WORDSJAVA-991 is under development phase. I have asked for the ETA of this issue from our development team. As soon as any information is shared by them, I will be more than happy to share that with you.
Regarding WORDSNET-11310, unfortunately we cannot provide you any reliable estimate at the moment and this
issue is not likely to be fixed in the near future. The implementation of the fix of this issue has been postponed till a
later date. We will inform you as soon as there are any further developments.
We apologize for your inconvenience.
The issues you have found earlier (filed as WORDSJAVA-991) have been fixed in this .NET update and this Java update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
The issues you have found earlier (filed as WORDSNET-11310) have been fixed in this .NET update and this Java update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
Hi Wahaj,
Thanks
for your inquiry. I have tested the scenario and have managed to
reproduce the same issue at my side. For the sake of correction, I have
logged this problem in our issue tracking system as WORDSJAVA-1084. I
have linked this forum thread to the same issue and you will be notified
via this forum thread once this issue is resolved.
We are really very sorry for your
inconvenience.
Hi Wahaj,
Further to my last post, SimilarSignatureLines.docx has incorrect signatures. MS Word can’t verify them and when this document is exported to Pdf using MS Word, “recoverable signature” message still exists. See the attached image for detail.
So while converting this document to pdf using Aspose.Words, it puts “Signature is invalid” line instead of Word’s “Recoverable Signature”. Our product team will check the possibility of this fix. Once we have
any information about this, we will update you via this forum thread.
Please let us know if you have any more queries.
The issues you have found earlier (filed as WORDSJAVA-1084) have been fixed in this .NET update and this Java update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.