Good day -
We use Aspose PDF to convert PDF to Word format.
There are instances where PDF documents don’t convert, but Aspose does not throw a catchable error. Rather, we seem to get stack overflow errors which are difficult or impossible to handle.
We use ColdFusion but the options are pretty basic:
<cfset var docSaveOptions=createObject(“java”,“com.aspose.pdf.DocSaveOptions”).init()>
<!-- doc: 0, docx: 1 —>
<!— textbox: 0, flow: 1 —>
I’ve attached two PDF documents which cause this error.
These are sent by customers and admittedly they appear to be poorly created, particularly when highlighting blocks of text with the mouse. I don’t necessarily expect Aspose PDF to be able to convert them cleanly (though it would be nice!) but I believe there should be a way to gracefully handle them rather than running out of stack space.
Is there a way that Aspose could detect this issue and throw it before encountering a stack overflow?
Good day -
Thank you for running this Nayyer.
I just upgraded Aspose 10.3.0 from the previous version. It appears as though you may have run the examples in textbox mode. I am now able to convert using textbox mode; however, our customers require that flow be maintained, so we have flow mode set:
Are you also able to convert using flow mode? When I run one of the documents, it does so without creating a stack overflow error; however the text is all over the place. I’ve attached the document to this message.
our issue tracking system as PDFNEWJAVA-34888. However when badpdf2.pdf is converted to DOCX format, there are formatting issues in resultant file. For
the sake of correction, I have separately logged it in our issue tracking system as PDFNEWJAVA-34889. We
will investigate these issues in details and will keep you updated on the status
of a correction.
We apologize for your inconvenience.