I understand your sincere intentions.
But only from Aspose’s point of view.
I don’t know what your business policy is, but maybe you wasted too much time with ticketing for even basic issues in the package ?
Even assuming you can clear all the issues in this May version, I will be waiting for 5.5 months.
First of all, please answer the following (as a customer)
- When will it be available ?
- So the license you issued is useless for almost half a year. What are you going to do about this?
- I’ve been wasting my time with bug reports and being asked to wait and things are stalled here. Who do I talk to about this?
I’m stumped here too.
@DK1_Lee
We are afraid that we cannot provide any promising ETA since the development is in process for the issue and due to complex nature of this issue, it can and is taking significant amount of time. We would like to add that issue may seem very basic as an end user of the API but, it may be quite complex due to API components involved in it. As we already shared, Aspose.PDF is quite massive API with hundreds of components and complex issues can take this much time to get fully resolved.
In such case, you can create a post in our Purchase forum to contact our business and sales team if they can offer you some compensation or extension in your license considering the whole situation.
You can launch create a post in our Complaint forum category if you want to raise your concerns on next level.
However, please note that - as mentioned in our previous replies as well - we can only raise the issue priority to some extent in free support model where tickets are prioritized on first come first serve basis. We have mentioned these policies as well on our site because we believe it is the fairest policy. In case of urgent issues, we recommend using our priority support model where issues are taken with highest priority and are resolved on urgent basis.
We do understand that only an apology for this delay and inconvenience won’t be enough for you in a situation like this. However, we also want to assure you that we do take every issue as serious as it should be taken and work on resolving it as per our schedule to keep the API up to date and improved in every monthly release. A lot of our customers are using our APIs and are aware of this model.
Please feel free to let us know in case you want to share more concerns. In the meanwhile, we will keep you posted about the progress against ticket resolution.
Hello.
I’ve been waiting for a resolution to this issue for over 6 months now, and I’m very disappointed to hear the final answer that I don’t even know when it will be resolved.
I’ve thought about posting more on the forums, as you’ve done in your comment about this situation, but I feel like it doesn’t solve the real problem, and it’s a way to frustrate a lot of people, so I’d like to end this in a realistic way.
I’d like to end this with a payback, and if you want the account number, just point me to where you want it and I’ll get it to you.
You’ve done a great job walking us through a difficult and unsolvable problem.
I wish you many other good things.
Good luck !
@DK1_Lee
We have already been apologizing for the delay and inconvenience you have been facing due to this error. Speaking of the investigation against this issue, it is already under the phase of the development. There are more than seven (7) sub tasks that have been created in order to implement the changes required for the support. Aspose.PDF is a massive API and it has quite a number of modules. For certain issues and requirements, we have to change core parts and modules of the API that takes significant amount of time.
Nevertheless, we will keep investigating the ticket and include the fix in future version(s) of the API.
It is really unfortunate to hear this from you. Please allow us to gather some information related to your above request and we will let you know further about the process.
Hello.
I’ve been waiting for 2 more months after being told you don’t know when this will be resolved.
I’ve been waiting for over 8 months now, and you’re asking me to wait again.
Maybe it’s not meant to be this time.
Let’s end this with a payback.
Please let me know where to send the account number for the refund. ( my email or this page )
I’ll give you 2 weeks to do so.
If you make me wait any longer, I will have to do something other than this forum ?
(I can’t help it if you do it again, but …) That seems undesirable.
If you crush me without telling me where to send the account that will give me the payback,
I will have someone else contact you.
It didn’t work out this time, but let’s finish this one beautifully for next time.
Keep up the good work.
@DK1_Lee
We would like to share with you that the tasks which were blocking the ticket have been resolved and with internal (unpublished) testing, we have obtained attached result after extracting text from the PDF.
56235_output.zip (2.8 KB)
The mathematical summation symbol ∑ (sigma) is not correctly parsed, because ToUnicode CMap does not have a mapping to the code used in the content stream.
Nevertheless, the estimated timeframe to ship the fix in the API is August 2024, assuming all other integration tests and analysis proceed as expected. Technical difficulties could affect this timeframe, though we hope this will not be the case. Please do let us know if this suits you or you still need a refund. We will proceed accordingly without making you wait any longer. We sincerely apologize for the inconvenience and delay you have been facing.
Yes, please let me go through the refund process.
Where can I send my refund account?
Wishing you many good things…
@DK1_Lee
I’m sorry to hear about your trouble. I have issued a full refund of order ID 231216025534. Please expect the money to be returned to your card ending in 2970 within the next few days.
The issues you have found earlier (filed as PDFJAVA-43399) have been fixed in Aspose.PDF for Java 24.9.