0

I have an xsl-fo xslt file, and it generates blank pages, along with the standard "An error exists on this page. Acrobat may not display the page correctly. Please contact the person who created the PDF document to correct the problem" error message.

I found that the issue was due to the text I was writing into the pdf contained dashes "–" and when I removed characters, the pdf was rendered successfully.

does anyone know why this "–" character would cause the xsl-fo pdf process should fail? everything I have read says this is not a special character and I shouldn't worry about encoding it.

Update here is a link to the Aspose forum's post I created: http://www.aspose.com/community/forums/permalink/593149/593149/showthread.aspx#593149

Update #2 I found the issue was not the forward slash, but an encoding issue with dashes (I have updated the questions content, sorry for the confusion) at this point i am still looking for an answer, but I confused the differences between my working xml data, and my not working xml.

Nathan Tregillus
  • 6,006
  • 3
  • 52
  • 91
  • Is the slash only bad in the VariableName or also in the VariableLabel? – mkl Dec 10 '14 at 18:12
  • We need to see what the template named `variableLabel` does. – Martin Honnen Dec 10 '14 at 18:31
  • no, I have other examples from customers where the slash is in other text components. this was the clearest, simplest steps to recreate I could find. @MartinHonnen I am not sure what you mean by "see what the template named variableLabel does" we are taking the xml value above, and injecting it into an fo:table cell. that's it. – Nathan Tregillus Dec 10 '14 at 18:47
  • @MartinHonnen I have added the whole for-each block. let me know if that was the information you were wanting. – Nathan Tregillus Dec 10 '14 at 18:52
  • Are you producing a simple PDF or are you producing a fillable PDF Form and using the label as the name of the field? – Kevin Brown Dec 10 '14 at 19:15
  • I am creating a readonly pdf of the data found in the xml. no input fields are added to the form. Thanks for the question @KevinBrown – Nathan Tregillus Dec 10 '14 at 20:02
  • You have `` in there which passes on the elements so I would like to see what that template does. – Martin Honnen Dec 10 '14 at 21:26
  • Well, while I would like to also see the template ... I can think of nothing in the world that would cause issues as you mention short of trying to create fields in the PDF in an Acroform. Having a "/" or any other character in a text string is nothing short of what seems to be a bug in the software you are using. – Kevin Brown Dec 11 '14 at 02:35
  • yeah, I am thinking the same thing. I linked this stack overflow to the company (Aspose) but it looks like their link functionality doesn't work – Nathan Tregillus Dec 11 '14 at 18:55
  • Sorry guys, I found the issue was not the forward slash, but some older data that did not have an encoded dash. when I removed the forward slash, the underlying data was saved in an encoded format that corrected the issue. *however* I am confused why the "–" character would blow up my pdf generation so spectacularly! – Nathan Tregillus Dec 12 '14 at 20:44
  • Your confusion is perfectly understood. it shouldn't. Your have done the right thing and reported as a bug. – Kevin Brown Dec 17 '14 at 06:13

0 Answers0