Hi.
Hi Itamar,
Thanks
for using our API’s.<o:p></o:p>
I have tested the scenario and I am able to notice the same problem. For the sake of correction, I have logged this problem as PDFNEWNET-36725 in our issue tracking system. We will further look into the details of this problem and will keep you updated on the status of correction. Please be patient and spare us little time. We are sorry for this inconvenience.
is there any update on the ticket status?
Hi Itamar,
<span style=“font-size:10.0pt;font-family:“Arial”,“sans-serif”;
color:#333333;background:white”>The development team has been busy resolving
other priority issues and I am afraid the above stated problem is not yet
resolved. Nevertheless, as soon as we have some updates regarding its resolution, we would
be more than happy to update you with the status of correction. Please be
patient and spare us little time.<o:p></o:p>
We are sorry for this delay and inconvenience.
Hi there,
Hi Michael,
The development team has been busy resolving
other priority issues and I am afraid the issue reported earlier is not yet
resolved. Nevertheless, I have requested the team to share the ETA regarding
its resolution. As soon as we have some definite updates regarding its
resolution, we would be more than happy to update you with the status of correction.
Please be patient and spare us little more time.<o:p></o:p>
Furthermore, I cannot see Priority Support badge with your account and in case you have already purchased, please share the order ID so I can double check with sales team.
Hi Itamar,
As per our observations, the file contains “\0\0\0\0” characters with “11” at the end of the file. We can ignore the “\0\0\0” characters and write “11” only. Please acknowledge so we may proceed accordingly.
I accept.
Hi Itamar,
The issues you have found earlier (filed as PDFNEWNET-36725) have been fixed in Aspose.Pdf for .NET 9.3.0.
Blog post for this release can be viewed over this link
This message was posted using Notification2Forum from Downloads module by Aspose Notifier.