topic Re: [resolved] tJasperReportExec and Umlauts in Talend Studio

[resolved] tJasperReportExec and Umlauts

Anonymous — Tue, 19 May 2015 08:37:28 GMT

Hi all,
I managed to create a job that loops through a MySQL-Table and saves PDFs of a Jasperreport for each ID.
When I have Jaspersoft Studio create the .jasper files, the output of tables aren't correct. For example cells aren't centered or font is too big where I made it smaller to fit the cell.
When I delete all .jasper files and have Talend tJasperReportExec create them, format is perfect, but in text fields I have no Umlauts. Text in tables that comes from Database is fine.
Text Fields are styled and font is Sans serif, nothing special here.
I use:
Jaspersoft Studio 6.04 (with compatibility set to 5.5.1 or other makes no difference)
Talend Open Studio for Data Integration 5.6.1
tJasperReportExec 1.11
All local on Windows 8.1 PC.
If you need more information I'll be happy to provide it.
Thanks a lot in advance.

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Mon, 25 May 2015 05:14:04 GMT

Hi,
Did you get tJasperReportExec component from Talend Exchange:https://exchange.talend.com/#marketplaceproductoverview:gallery=marketplace%252F1&pi=marketplace%252F1%252Fproducts%252F549%252Fitems%252F819?
Have you already checked component reference?
Best regards
Sabrina

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Mon, 25 May 2015 13:20:47 GMT

I will check that. Actually I am convinced it should work because it does it for my current project.

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Tue, 26 May 2015 10:47:53 GMT

Thank you for your replies. Yes, I've doublechecked the reference and the forums both of Jaspersoft and Talend, but I couldn't find anything helpful.
I opened the binary files in a normal editor and found this, which should be "für" and "Größenverteilung":
.jasper from Jaspersoft Studio:
zur Ausbildung fÃ¼r Ihr Unternehmen and Die GrÃ¶ÃŸenverteilung
.jasper from Talend tJasperReportExec
zur Ausbildung fÃƒÂ¼r Ihr Unternehmen and Die GrÃƒÂ¶ÃƒÅ¸enverteilung
I know it's a binary, but to me it looks as if tJasperReportExec somehow doubles the Umlauts while creating the jasper, so it can't be decoded correctly.
Is this helpful?
Other than that I'm as convinced it should work as you are, jlolling, because nobody else asked for help. This tells me I'm the culprit, but I have no idea where to look.
Thanks again in advance.

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Wed, 27 May 2015 06:45:22 GMT

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).

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Wed, 27 May 2015 06:50:43 GMT

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:

<?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>

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Wed, 27 May 2015 15:29:41 GMT

Unfortunately it has nothing to do with MySQL. Text coming from Database is fine. I use "Text Field" and those drive me nuts.
Here is the .jrxml I use:

<?xml version="1.0" encoding="UTF-8"?>
<!-- Created with Jaspersoft Studio version 6.0.4.final using JasperReports Library version 6.0.0  -->
<!-- 2015-05-27T15:50:07 -->
<jasperReport xmlns="" xmlns:xsi="" xsi:schemaLocation=" " name="test_pdf" pageWidth="595" pageHeight="842" columnWidth="555" leftMargin="20" rightMargin="20" topMargin="20" bottomMargin="20" uuid="9026e51d-fac0-496b-b200-62c15060a142">
	<property name="com.jaspersoft.studio.unit." value="pixel"/>
	<property name="com.jaspersoft.studio.unit.columnWidth" value="pixel"/>
	<property name="com.jaspersoft.studio.data.defaultdataadapter" value="BM_Chemie"/>
	<style name="Table_TH" mode="Opaque" backcolor="#F0F8FF">
		<box>
			<pen lineWidth="1.5" li

To see the whole post, download it here
OriginalPost.pdf

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Wed, 27 May 2015 16:13:32 GMT

Did you trieb to Let the component create the jasper file? please provide only the jrxml file and Run the Job again.

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Wed, 27 May 2015 16:22:46 GMT

Sorry I didnt read your post fully. My last answer is useless. Are the Talend Job runs on the same Maschine like your Jasperstudio?
where Do you Run the talend job?
Did you try to run a small test Report like my suggestion?

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Thu, 28 May 2015 09:40:07 GMT

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?

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Thu, 28 May 2015 11:49:22 GMT

Ah, ok this could be caused by the read of the jrxml file with the wrong character set. I have dived in the source code of the library and see there is no file encoding setting and also not for the writing of the file. I will check if I can take care the file will always read with UTF-8.
I come back here when I can reproduce this and have a solution.
As long as we have a solution you could try bundles to add localised texts.

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Thu, 28 May 2015 22:06:21 GMT

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:

System.setProperty("file.encoding", "UTF-8");

before the jasper comp. It changes the default encoding and this way your file should be read correctly.

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Thu, 28 May 2015 23:20:46 GMT

I have made some slight changes to this component to be sure the JRXML file will be read in UTF-8 encoding regardless what is set as default encoding. I habe uploaded an new test release (1.16) here:
http://jan-lolling.de/talend/components/tJasperReportExec.zip
Could you give it a try?

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Fri, 29 May 2015 13:50:59 GMT

Perfect, that's the solution. Thank you very much indeed. The reports run fine and show Umlauts in all their glory.
In my "real" report only one damn Text Field refused cooperation, but with this one I started to play with the encodings, so no problem here. The rest is as it should.
So thanks again and have a nice weekend!

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Fri, 29 May 2015 16:30:43 GMT

Great to hear. Did you tried the piece of code or the new release of the component. Actually both ways handles the same problem (the new release does not need the global setting and should be the one for further development).

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Mon, 01 Jun 2015 15:23:40 GMT

I tried the 1.16 Release from your link, because I missed your other post (and was wondering which piece of code you were talking about).
But I'll test the code, too, just a little bit busy at the moment.
The .jrxml files are all utf-8, I checked this when I started. All I can say is I didn't change anything in configuration, but that doesn't say I can't do anything wrong.
I'll test the code tomorrow!

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Mon, 01 Jun 2015 15:30:35 GMT

I meant this piece of code in a tJava:
System.setProperty("file.encoding", "UTF-8");
But you do not have to test it. The update of the component is the better way.
I will update the release also in Talend Exchange.
Thanks a lot for your tests and your feedback!

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Tue, 02 Jun 2015 14:15:47 GMT

Thank you very much for your help I'll set the thread as solved then.

Re: [resolved] tJasperReportExec and Umlauts

Anonymous — Fri, 18 Mar 2016 15:40:07 GMT

gsczuka....can you post a screenshot of your tJasperReportExec component settings? i'm trying to do the same thing as you, but am having a difficult time with the parameters