Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
1 Solution
Accepted Solutions
To be in danger driving you creasy here is my own test and it convinced my, there is something wrong with your way to write the jrxml file:
The way the wrong encoding is showing is very typical for a reading of an text file with the wrong char set.
Could you check if the char set of the jrxml file is UTF-8. Perhaps you open it with UltraEdit with fix setup UTF-8 encoding.
Please test if it works if you add a tJava with this code:
before the jasper comp. It changes the default encoding and this way your file should be read correctly.
The way the wrong encoding is showing is very typical for a reading of an text file with the wrong char set.
Could you check if the char set of the jrxml file is UTF-8. Perhaps you open it with UltraEdit with fix setup UTF-8 encoding.
Please test if it works if you add a tJava with this code:
System.setProperty("file.encoding", "UTF-8");
before the jasper comp. It changes the default encoding and this way your file should be read correctly.
OK, I have tested it and I can ensure you it works.
Back to your problem.
Did you spot encoding errors in JasperStudio?
There are always possible problems with the encoding in the MySQL database which is per default set up with charset LATIN1. I suggest you reconfigure the database (or even the tables with UTF-8).
Back to your problem.
Did you spot encoding errors in JasperStudio?
There are always possible problems with the encoding in the MySQL database which is per default set up with charset LATIN1. I suggest you reconfigure the database (or even the tables with UTF-8).
OK, I have tested it and I can ensure you it works. The PDF is created by a simple Talend job made of a tMysqlConnection and tJasperReportExec.
Back to your problem.
Did you spot encoding errors in JasperStudio?
I suggest you build a very simple job - like mine - and test the encoding straight forward to be sure you are at the right place to fix the problem. Perhaps you can post here your job design.
There are always possible problems with the encoding in the MySQL database which is per default set up with charset LATIN1. I suggest you reconfigure the database (or even the tables with UTF-8).
Here my very simple jrxml:
Back to your problem.
Did you spot encoding errors in JasperStudio?
I suggest you build a very simple job - like mine - and test the encoding straight forward to be sure you are at the right place to fix the problem. Perhaps you can post here your job design.
There are always possible problems with the encoding in the MySQL database which is per default set up with charset LATIN1. I suggest you reconfigure the database (or even the tables with UTF-8).
Here my very simple jrxml:
<?xml version="1.0" encoding="UTF-8"?>
<!-- Created with Jaspersoft Studio version 6.1.0.final using JasperReports Library version 5.5.1 -->
<!-- 2015-05-27T07:49:23 -->
<jasperReport xmlns="http://jasperreports.sourceforge.net/jasperreports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jasperreports.sourceforge.net/jasperreports http://jasperreports.sourceforge.net/xsd/jasperreport.xsd" name="test_umlauts" pageWidth="595" pageHeight="842" columnWidth="555" leftMargin="20" rightMargin="20" topMargin="20" bottomMargin="20" uuid="262988c5-a8bf-4cc7-b628-3767e070f2fa">
<property name="com.jaspersoft.studio.data.defaultdataadapter" value="local_mysql"/>
<queryString>
<!]>
</queryString>
<field name="umlauts" class="java.lang.String">
<fieldDescription><!]></fieldDescription>
</field>
<background>
<band splitType="Stretch"/>
</background>
<title>
<band height="79" splitType="Stretch"/>
</title>
<pageHeader>
<band height="35" splitType="Stretch"/>
</pageHeader>
<columnHeader>
<band height="61" splitType="Stretch">
<staticText>
<reportElement x="190" y="20" width="100" height="30" uuid="acad6421-f00d-4552-a092-69974176f454"/>
<text><!]></text>
</staticText>
</band>
</columnHeader>
<detail>
<band height="125" splitType="Stretch">
<textField>
<reportElement x="0" y="20" width="550" height="90" uuid="f45d6063-16f1-4d35-8cd5-7380e1a7584c"/>
<textElement textAlignment="Center" verticalAlignment="Middle">
<font size="26"/>
</textElement>
<textFieldExpression><!]></textFieldExpression>
</textField>
</band>
</detail>
<columnFooter>
<band height="45" splitType="Stretch"/>
</columnFooter>
<pageFooter>
<band height="54" splitType="Stretch"/>
</pageFooter>
<summary>
<band height="42" splitType="Stretch"/>
</summary>
</jasperReport>
Yes, both Jaspersoft Studio and Talend run on the same office computer.
The small test I made first was an extract from a report I made and already delivered before. My first report, though.
This was made out of a lot of graphics and tables, numbers coming from database, and text as introduction to chapters, which I wrote directely into text fields. When I realized that tJasperReportExec created pdfs do not look like Jaspersoft pdfs I made that extract with one table and a text field from my report to test.
Now I tested your .jrxml file. I added a "fünf" to the "umlauts" in your static field. Connected to my database in your text field and added a text field with text. When tJasperReportExec creates the .jasper file it looks like this:
Surprisingly text written in Static Text is fine, text coming from database is fine, text written in Text Field is not.
Not to mention that pdfs from Jaspersoft Studio are always correct. So I'm lost here. Do I miss some settings?
The small test I made first was an extract from a report I made and already delivered before. My first report, though.
This was made out of a lot of graphics and tables, numbers coming from database, and text as introduction to chapters, which I wrote directely into text fields. When I realized that tJasperReportExec created pdfs do not look like Jaspersoft pdfs I made that extract with one table and a text field from my report to test.
Now I tested your .jrxml file. I added a "fünf" to the "umlauts" in your static field. Connected to my database in your text field and added a text field with text. When tJasperReportExec creates the .jasper file it looks like this:
Surprisingly text written in Static Text is fine, text coming from database is fine, text written in Text Field is not.
Not to mention that pdfs from Jaspersoft Studio are always correct. So I'm lost here. Do I miss some settings?