planplus

Hi, Ive got a very simple report where we have a pageHeader, detail and pageFooter band. The only thing in the detail band is a table (componentElelment). The report generates fine as long as the number of rows in that table is low enough so it doesnt need to overflow (about 50 or so rows). Once the table is larger than that then we get into that infinite loop condition. If I switch the isPrintWhenDetailOverflows to false then we dont get the infinite loop issue and the report will generate however it generates a second page and the only thing on that second page is the Header & Footer, No continuation of the detail band and the table. Im assuming that when the isPrintWhenDetailOverflow is true the engine sees its overflowing and instead of picking up with the next row of the table on the next page its trying to generate the whole table again on the next page and sees it needs to overflow and so on and so on. Should we be using that table differently than just putting it in the detail band. I tried removing the detail band and putting the table in a group but that resulted in the same infinie loop. Thanks in advance.

This turned out to be a java issue and not specific to jasper reports. If you create a Locale object with a language and country combination that is not in the list of available Locales it will put that currency code text in front of a number formatted with the NumberFormat.getCurrencyInstance class.

Hi, I have been playing around with setting the locale in the jasper report. We have our own formatter that does much the same thing as the java currency formatter but would rather use the build in functionality of java/jasper reports. However on certain combinations of language and country I get some strange results when a Double number has a currency pattern. For example, if I create a new Locale with "fr" lang and "FR" country I get a nicely formatted amount with the euro symbol preceeding it, spaces instead of commas for groupings and the comma as the decimal point. If I change that local to "fr" lang and "CA" country I get something like this CAD123,456.78 Ive seen a different local come up with something like EUR123,456.78 Any Ideas? Thanks in advance.

Figured it out. The message was saying for the font I picked, in this case Times-Roman, the encoding is not supported. If I pick a font with chinese characters it runs fine. I also downloaded iTextAsian.jar, dont know if that helped or not. When I generate html instead of pdf the text is showing different chinese characters. Wonder if the web page is using a different font.

Hi, Ive searched the forums and cant find anything on this particular error. I think it might be a java problem and not really a jasper problem but thought I would start here since its an exception when trying to export a jasper report to pdf. I am trying to output chinese characters and have setup a single text field with the settings found on the unicode jasper sample. The section of jasper xml is... Code: <textField> <reportElement x="74" y="0" width="423" height="22"/> <textElement textAlignment="Center" verticalAlignment="Middle"> <font fontName="Arial" size="16" isBold="true" pdfFontName="Times-Roman" pdfEncoding="Identity-H" isPdfEmbedded="true"/> </textElement> <textFieldExpression class="java.lang.String"><![CDATA[$P{ss}.getLabel($F{title}, $P{jurisdiction}, $P{language})]]></textFieldExpression> </textField> When the JasperExportManager.exportReportToPdfFile(jasperPrint, destFile); method is run I get an exception saying .. Code:[code] ExceptionConverter: java.io.UnsupportedEncodingException: Identity-H at sun.io.Converters.getConverterClass(Unknown Source) at sun.io.Converters.newConverter(Unknown Source) at sun.io.CharToByteConverter.getConverter(Unknown Source) at java.lang.StringCoding.encode(Unknown Source) at java.lang.String.getBytes(Unknown Source) at com.lowagie.text.pdf.PdfEncodings.convertToBytes(PdfEncodings.java:197) at com.lowagie.text.pdf.Type1Font.<init>(Type1Font.java:278) at com.lowagie.text.pdf.BaseFont.createFont(BaseFont.java:389) at com.lowagie.text.pdf.BaseFont.createFont(BaseFont.java:342) at com.lowagie.text.FontFactory.getFont(FontFactory.java:225) at net.sf.jasperreports.engine.export.JRPdfExporter.getChunk(JRPdfExporter.java:1396) . . . Is there something simple im missing, a jar file or something that would cause java not to think that encoding is valid? Thanks in advance.