0

I recently upgraded from iReport 3.0.0 to iReport 5.6.0. After the upgrade some of the text in my report wouldn't show up in the generated PDF file. I messed around a bit and found out that on making the textfields bigger, the text shows up. But that is not a solution for me, since I have over 50 reports that would need editing. Also increasing the size of the textfield messes with my whole report.

I think it has something to do with the PDF font. In iReport 3.0.0 I used Helvetica as my font; but I learned that in iReport 5.6.0, the PDF font is deprecated.

I feel like this has also something to do with the fact that I converted .jasper files to .jrxml files in 5.6.0. I don't have any idea of how I can fix this. Could someone help me figure out what I'm doing wrong.

Alex K
  • 22,315
  • 19
  • 108
  • 236
appmuffin
  • 1
  • 2
  • Have you updated the jasper-report jar as well? – Petter Friberg Jan 27 '16 at 20:52
  • You should use font-extension to include your font correctly in pdf, please see for example: http://stackoverflow.com/questions/34271686/jasper-report-truncates-text-before-filling-the-whole-text-field – Petter Friberg Jan 28 '16 at 23:04
  • see also this seems different but it always on how to render font correctly in pdf.. http://stackoverflow.com/questions/34041619/jasper-reports-pdf-doesnt-export-cyrillic-values – Petter Friberg Jan 28 '16 at 23:14
  • thanks @PetterFriberg! but I have a new problem now. Whenever i save the report, the textFieldExpression class attribute changes to a java.lang.string. Also, the compiler language does not save. I have to manually enter it each time I save the report. Is this a bug I am not aware of? – appmuffin Jan 29 '16 at 16:24
  • textFieldExpression attribute is not needed anymore (jasper report v5,6), as far as language it should save (there is a default settings in which language to start... but does not seem to function so well), need always to switch from groovy to java.... – Petter Friberg Jan 29 '16 at 16:33
  • What settings do you in options >> compatibility? – Petter Friberg Jan 29 '16 at 16:35
  • I have Last Version. I tried with 3.1.0 but it doesn't work. – appmuffin Jan 29 '16 at 17:33

0 Answers0