foo1301

That's interesting and opens up a new possibility (and yes, you're right about the JDK versions). I'll have a look at that - thank you very much, teodor. Post Edited by foo1301 at 08/24/2009 13:20

Hello teodor, this font.jar contains tthe two TT-fonts (vcarial.ttf and vcarialbd.ttf) we are using with JR: <reportFont name ="HeaderFont" isDefault ="false" fontName ="VCArial" size ="8" isBold ="true" isItalic ="false" isUnderline ="false" isStrikeThrough ="false" pdfFontName ="vcarialbd.ttf" pdfEncoding ="Cp1252" isPdfEmbedded ="true"/> The fonts are initialized by: final InputStream isArial = getClass().getResourceAsStream("/vcarial.ttf"); final InputStream isArialBold = getClass().getResourceAsStream("/vcarialbd.ttf"); Font.createFont(Font.TRUETYPE_FONT, isArial); Font.createFont(Font.TRUETYPE_FONT, isArialBold); isArial.close(); isArialBold.close(); This solution indeed solved the font problems we had that time, so i'm quite sure it always worked as intended. It just happened with the Websphere upgrade that a similar (above mentioned) font problem occured, and i have no further idea to solve it.

Hello jasperfolks, we are using jasperreports 1.3.4 (with itext 1.2.1) in production for several years now for generating pdf sheets. Developing takes place in a windows, production in a unix environment using Websphere. In the beginning we had severe problems with texts in textfields becoming truncated in unix, whereas they have been displayed correctly in windows during development. It turned out that we had to put a distinct font into a jar file and adding this one to the classpath. Recently we upgraded our production environment from Websphere 5 to Websphere 7 and suddenly the mentioned problem arose again. As an example, a date "04.05.2009" is truncated to "04.05.200"; as far as i have seen at most one character is truncated. The software that uses jasperreports is designed in a way that it cannot even start if the font.jar cannot be found, so this shouldn't be the cause. We have tried to upgrade versions (jasperreports to 2.0.5 and itext to 2.0.8; higher versions led to compatibility issues) setting the net.sf.jasperreports.export.pdf.force.linebreak.policy to true checking the fonts in the resulting pdf; seemed okIt is remarkable that the upgrade of Websphere (and that upgraded the jdk version from 1.4 to 5.0 (possibly 6 - don't know for sure)) with no other software change caused the problem. Possibly it is some kind of different rounding behaviour of the result of a small jdk method that changed with the jdk version? Any idea ? Thank you in advance