Can not read the text of Invoice image of jpg extention.The particular image is attached.
Hi Sudip,
Thank you for considering Aspose APIs.
First of all, your sample is actually a BMP stored with incorrect extension. Anyway, I have evaluated your presented scenario while using the latest version of Aspose.OCR for .NET 2.4.0, and was able to notice the low accuracy rate for the recognition process. I will try to tweak the configurations to get better results, and post my solution here for your reference.
Hi Sudip,
This is to inform you that we have logged a formal investigation in our database to review your sample in order to improve the accuracy of the recognized text. The ticket Id for your future reference is OCR-34007. Please spare us some time to properly analyze the problem cause, and to provide the fix at earliest possible. In the meanwhile, we will keep you posted with updates in this regard.
Please note, if you wish to read some particular portion from the provided image then we would suggest you to use the Custom Recognition Blocks.
Thanks for your suggestion.I am waiting for your solution.Thanks in advance for that.
Hi Sudip,
Thank you for your patience.
We have analyzed the ticket logged earlier as OCR-34007, and have identified the problem cause as the bad splitting of touching characters and the low recognition quality of some characters. In order to provide the fix, we have to first enhance the core so we have attached the blocking tasks to the aforesaid ticket. As soon as we have made significant progress in resolving the the said issues, we will notify you here with the estimated release schedule for the fix.
Ok…Please try to resolve it ASAP because I have some urgency for client’s requirement.
Hi Sudip,
I have checked the latest status of the ticket OCR-34007. The product team hasn’t assigned a fix version to this ticket, however, the blocking tasks are scheduled for the 2nd quarter of 2015. Let me discuss the matter internally to estimate the release schedule for the fix. I will post here as soon as I have more news for you.
The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for JasperReports 18.3 update.