<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: [resolved] Encoding problem with TrestClient in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/resolved-Encoding-problem-with-TrestClient/m-p/2368690#M131923</link>
    <description>The problem was the default encoding for java.
&lt;BR /&gt;Forcing it with "-Dfile.encoding=UTF-8" for the JVM arguments works.
&lt;BR /&gt;Added in advanced params of Execute tab.</description>
    <pubDate>Fri, 06 May 2016 12:27:38 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2016-05-06T12:27:38Z</dc:date>
    <item>
      <title>[resolved] Encoding problem with TrestClient</title>
      <link>https://community.qlik.com/t5/Talend-Studio/resolved-Encoding-problem-with-TrestClient/m-p/2368689#M131922</link>
      <description>&lt;P&gt;Hi All,&lt;BR /&gt;&lt;BR /&gt;When I run my job from my windows client, I get no problem with any character.&lt;BR /&gt;When I export the job and run it on a MAC OS 10 server, all the special characters are replaced and are bad.&lt;BR /&gt;I force the charset ot the Tresclient with&amp;nbsp;"charset" as&amp;nbsp;"UTF-8" in HTTp Header (Advanced settings) but the problem is still there.&lt;BR /&gt;Any idea?&lt;/P&gt;</description>
      <pubDate>Fri, 06 May 2016 10:54:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/resolved-Encoding-problem-with-TrestClient/m-p/2368689#M131922</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-05-06T10:54:39Z</dc:date>
    </item>
    <item>
      <title>Re: [resolved] Encoding problem with TrestClient</title>
      <link>https://community.qlik.com/t5/Talend-Studio/resolved-Encoding-problem-with-TrestClient/m-p/2368690#M131923</link>
      <description>The problem was the default encoding for java.
&lt;BR /&gt;Forcing it with "-Dfile.encoding=UTF-8" for the JVM arguments works.
&lt;BR /&gt;Added in advanced params of Execute tab.</description>
      <pubDate>Fri, 06 May 2016 12:27:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/resolved-Encoding-problem-with-TrestClient/m-p/2368690#M131923</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-05-06T12:27:38Z</dc:date>
    </item>
  </channel>
</rss>

