Free Support Forum - aspose.com

PDF-to-Word - string index out of bounds

Hello, I’m using Aspose PDF 10.4.1 to convert PDF to Word (via ColdFusion):

<cfset var docSaveOptions=createObject(“java”,“com.aspose.pdf.DocSaveOptions”).init()>
<!-- doc: 0, docx: 1 —>
<cfset docSaveOptions.setFormat(1)>
<!— textbox: 0, flow: 1 —>
<cfset docSaveOptions.setMode(1)>
<cfset docSaveOptions.setRecognizeBullets(true)>
<cfset pdf=createObject(“java”,“com.aspose.pdf.Document”).init(tempFile)>
<cfset pdf.decrypt()>
<cfset pdf.save(tempDocXFile,docSaveOptions)>
<cfset pdf.close()>
On the attached file, in Aspose PDF10.3.x, the file converted but all the letters were upside down. When we upgraded to 10.4.1, we get an error:


				<tr>
				<td class="struct" style="cursor:pointer;" title="click to collapse"><font face="Courier New" size="1">StackTrace</font></td>
				<td><font face="Courier New" size="1">
				java.lang.StringIndexOutOfBoundsException: String index out of range: 437
at java.lang.String.charAt(Unknown Source)
at com.aspose.doc.ml.MlParagraphConverter.addParagraph(Unknown Source)
at com.aspose.doc.ml.Wbody.accept(Unknown Source)
at com.aspose.doc.ml.Wdocument.accept(Unknown Source)
at com.aspose.doc.ml.DocxConverter.convert(Unknown Source)
at com.aspose.pdf.internal.p687.z8.m15(Unknown Source)
at com.aspose.pdf.internal.p37.z2.m1(Unknown Source)
at com.aspose.pdf.z19.m1(Unknown Source)
at com.aspose.pdf.ADocument.m1(Unknown Source)
at com.aspose.pdf.Document.m1(Unknown Source)
at com.aspose.pdf.ADocument.save(Unknown Source)
at com.aspose.pdf.Document.save(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)</font></td></tr></tbody></table></blockquote>Please advise.  Thank you.<br>
String index out of range: 437

Hi there,

Thanks for your inquiry. I have tested your scenario with shared document using Aspose.Pdf for Java 10.4.1 and managed to observe the reported issue. For further investigation, I have logged an issue in our issue tracking system as PDFNEWJAVA-35007 and also linked your request to it. We will keep you updated via this thread regarding the issue status.

Please feel free to contact us for any further assistance.

<span style=“font-size:10.0pt;line-height:115%;font-family:“Arial”,“sans-serif”;
mso-fareast-font-family:Calibri;color:#333333;mso-ansi-language:EN-US;
mso-fareast-language:EN-US;mso-bidi-language:AR-SA”>Best Regards