Sure, the ticket information has been updated accordingly. We will surely share updates with you as soon as we have some.
I’m embarrassed to even ask my boss to wait more.
All 4 months of versions (23.11 to 24.2) are not handling this issue(PDFJAVA-43399) correctly.
I will send you the results of my tests on the current version (24.2).
We have not made any progress on this issue and it is causing a lot of problems in our schedule.
Please don’t delay any further.
TEST-RESULTS(PDFJAVA-43399)-24.2.docx (51.3 KB)
Please accept our humble apologies for the delay and the inconvenience you may have been facing due to this issue. Please note that we can only prioritize the issues to some extent in the free support model. Otherwise, they are resolved on a first come first serve basis and resolution time depends upon the number of issues as well as complex nature of the issue itself.
Nevertheless, the ticket was already escalated by considering your concerns and its investigation is underway. The nature of the issue is complex and different sub-tasks have been created in our issue management system that need to be closed to implement the fix. Some of these sub-tasks are still open and are being worked on. As soon as we were able to ship the fix of this issue, we will inform you in this forum thread. We highly appreciate your patience and comprehension in this regard.
Thanks for the ticket.
In this case, if there was no bug, there would be no need for a ticket.
This is a text extraction bug ticket, not for a special add-on for our business.
Shouldn’t it be considered according to its content ?
Note) In the file I attached above, I’ve included a little example of how it was handled correctly in another package.
Would you please specify that another package as well so that we can check from that perspective as well?
Sometimes, issues are related to specific type of PDF documents and they are resolved only for those PDF files. Please note that PDF is a dynamic and massive file format in terms of its structure and complexity. Even two identical PDF document can differ in terms of their structures. The ticket was logged to investigate the PDF document and add support in the API to deal with such kind of PDFs for text extraction.
- another package
com.itextpdf
itextpdf
5.5.13.3
public static void main(String[] args) throws IOException {
File file = new File("GAN-2111.15166.pdf");
PdfReader reader = new PdfReader(file.getPath());
PdfReaderContentParser parser = new PdfReaderContentParser(reader);
TextExtractionStrategy strategy;
for (int i = 1; i <= reader.getNumberOfPages(); i++) {
strategy = parser.processContent(i, new SimpleTextExtractionStrategy());
System.out.println(strategy.getResultantText());
}
reader.close();
}
- I think ASPOSE is more expert on PDF format, so if you have any recommendations, I will follow them. I know it’s hard, but every time you solve a problem, you’re moving up a level. Cheers !!.
Thanks for providing the requested information and sharing kind feedback. We have updated the ticket information as per the details provided by you lately. We are afraid that we are not in a position to share any recommendations or workaround at the moment because ticket is still under the phase of investigation. Various API processing modules are being worked on in order to get this issue sorted out. As soon as we have some updates worth-mentioning, we will let you know via this forum thread. Your patience is highly appreciated in this regard.
I don’t know if you have the willpower to solve the problem of extracting the text I posted in this thread.
Even if it is fixed in this version, I’ve been waiting 4.5 months for it.
Hopefully it will be fixed in this version.
Also, after purchasing your package, my business has been held up by the bug, and the only thing I’ve done is report the bug.
I ask for the same treatment for this package license.
I hope you can resolve both the bug issue and the license issue.
I don’t know what to report to my boss.
I hope everything works out…
P.S. Please note that the PDF file we used to report the bug in this thread is not specially created by us, it is an example that can be easily found on the internet.
As shared earlier, the issue is under the phase of the investigation and we are afraid that it is taking time longer than expected because we need to investigate various module of text extraction engine of the API. The original task has dependency upon various sub tasks which were generated to address the issue internally.
We do apologize for the inconvenience and delay you have been facing. However, we are trying our best to deal with this issue and incorporate its fix. We will inform you once we have further updates about the ticket resolution. Please spare us some time.
Hello.
I bought the package and never got to use it, but your kindness has brought me this far, hasn’t it ?
However, I don’t think I can continue with apologizing, sorry, etc., I was trying to talk to you in business terms, but it seems that you are still staying as a kindness.
This is going on about 5 months since you asked me to keep waiting .
(I’ve said this in the thread before this one, but all you can do is ask me to wait)
I guess there’s a line that needs to be drawn in business.
If you ask me to wait, I have to ask someone else to wait, and I feel like I’ve reached a line where I can’t do that anymore.
If you can’t come up with a business-like way to do this, I’m going to demand it.
We do understand your concerns and severity of the issue for you. We have been mentioning and sharing that the issue was under the phase of investigation. Please note that we have been working continuously on resolving the issue attached here. There are 5 sub-tasks which were made after the investigation and out of them, 2 are already resolved.
Please note that Aspose.PDF is a massive API and has hundreds of modules with dependencies on each other. In order to resolve this issue, we have to make core changes in our text extraction engine as well as other dependent modules. These are the main reasons that the ticket is taking more time than expected. Along with this issue, we are definitely working on other requests and enhancements parallel to this ticket.
Nevertheless, your concerns have been raised internally and ticket has also been escalated to a certain level of priority. We will inform you as soon as we have more updates about the resolution ETA.
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.
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 !
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.
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…
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.