Product maturity

Can you provide any information the various products maturity? for example, we have used the office and image to pdf conversion very successfully, and this appears to be reliable and robust. However, barcode is flaky, PCL to PDF unreliable and you appear to not recommend your own OCR for OCR’d PDF creation due to lack of maturity (and forums are full of failed conversions to be fixed)
We are trying to evaluate how much of the Aspose.Total we can actually use in production, and have concerns over some libraries, so a history would be useful

bits:
PCL to PDF unreliable. We are trying to evaluate how much of the Aspose.Total we can actually use in production, and have concerns over some libraries, so a history would be useful
Hi Bryan,

Thanks for using our API's.

Please share the source/input PCL files causing this problem, so that we can test the conversion in our environment. We are sorry for this inconvenience.

Hi Bryan,

Aspose.Barcode is matured enough to handle complex cases as well. Can you please share the details if you see any issue? We will be more than happy to fix it.

As far as Aspose.OCR is concerned, it has some limitations e.g. result is fine if you use images with 300 DPI or higher resolution however accuracy of OCR text tends to decrease with the decrease in resolution. Not all languages are supported and time taken to extract text is not up to mark for all customers. You can confidently use Aspose.OCR if you have high resolution images and want to use supported languages only.

Please share the issue with samples if you see any issue with Aspose.OCR.

Best Regards,

Hi

Barcode could not recognise Code 39 in build 7.2 - 7.5. This is a pretty serious screw-up. You have separately confirmed the PCL to PDF issue in a very basic PCL file.
If OCR is slower and less accurate than competition, what is the reason for launch?
We are already a customer, but I have grave concerns about how much of the toolset we can use going forward.

Hi Bryan,

Your mentioned barcode issue has already been resolved. Yes, Aspose.OCR is too young to satisfy all customers but still it is satisfying some customers who are using it in their applications.

As far as Aspose.Pdf is concerned, it is matured already and a large number of customers are using it with confidence. Can you please share your input PCL or the issue ID you are referring to? This will help us fix the issue and make Aspose.Pdf usable for your case also.

We are sorry for the inconvenience.

Best Regards,