<?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 Turkish Character Problem in Schema in Installing and Upgrading</title>
    <link>https://community.qlik.com/t5/Installing-and-Upgrading/Turkish-Character-Problem-in-Schema/m-p/2384405#M4920</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am newbie to Talend, so if my question seems too obvious please accept my apologies beforehand. I have just installed Talend Open Studio and tried to create metadata for a delimited file. After a few attempts I realized that, if the file contains Turkish Characters in the column headings Open Studio fails to create the schema and gives 'At least one item must exist in Schema' Error. This happens when I select correct encoding method which as ISO-8859-9, with this setting Open Studio shows Turkish characters in the headings and in the data correctly. If I select UTF-8 as the encoding method, then characters&lt;STRONG&gt; not shown correctly&lt;/STRONG&gt; but Schema can be created with wherever a Turkish character exists replaced by a "_". If I try to edit them and use Turkish characters in the column then I get an error saying the column name is not valid.When I check file's original format it seems to be ANSI - DOS/Windows.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would&amp;nbsp;appreciate any input or suggestions here. This is quite important for our local implementations.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards&lt;/P&gt;</description>
    <pubDate>Sat, 16 Nov 2024 09:45:14 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2024-11-16T09:45:14Z</dc:date>
    <item>
      <title>Turkish Character Problem in Schema</title>
      <link>https://community.qlik.com/t5/Installing-and-Upgrading/Turkish-Character-Problem-in-Schema/m-p/2384405#M4920</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am newbie to Talend, so if my question seems too obvious please accept my apologies beforehand. I have just installed Talend Open Studio and tried to create metadata for a delimited file. After a few attempts I realized that, if the file contains Turkish Characters in the column headings Open Studio fails to create the schema and gives 'At least one item must exist in Schema' Error. This happens when I select correct encoding method which as ISO-8859-9, with this setting Open Studio shows Turkish characters in the headings and in the data correctly. If I select UTF-8 as the encoding method, then characters&lt;STRONG&gt; not shown correctly&lt;/STRONG&gt; but Schema can be created with wherever a Turkish character exists replaced by a "_". If I try to edit them and use Turkish characters in the column then I get an error saying the column name is not valid.When I check file's original format it seems to be ANSI - DOS/Windows.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would&amp;nbsp;appreciate any input or suggestions here. This is quite important for our local implementations.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 09:45:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Installing-and-Upgrading/Turkish-Character-Problem-in-Schema/m-p/2384405#M4920</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T09:45:14Z</dc:date>
    </item>
    <item>
      <title>Re: Turkish Character Problem in Schema</title>
      <link>https://community.qlik.com/t5/Installing-and-Upgrading/Turkish-Character-Problem-in-Schema/m-p/2384406#M4921</link>
      <description>Hi,&lt;BR /&gt;Field names in schema must be compliant with Java namming rules. So, if you use header file to automatically build the schema, you need to change field names which generate the error you get.</description>
      <pubDate>Sun, 21 May 2017 23:24:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Installing-and-Upgrading/Turkish-Character-Problem-in-Schema/m-p/2384406#M4921</guid>
      <dc:creator>TRF</dc:creator>
      <dc:date>2017-05-21T23:24:54Z</dc:date>
    </item>
    <item>
      <title>Re: Turkish Character Problem in Schema</title>
      <link>https://community.qlik.com/t5/Installing-and-Upgrading/Turkish-Character-Problem-in-Schema/m-p/2384407#M4922</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks a lot for the answer. Actually, this will work for a file, but it is not very practical for a real project since we cannot control column names in the source systems or files. Is there any way to alter this? I tried to change Java default locale but not successful so far. It would be perfect if I can change Talend runtime parameters so that it would accept Turkish characters in the field names.&lt;/P&gt;</description>
      <pubDate>Sat, 27 May 2017 14:44:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Installing-and-Upgrading/Turkish-Character-Problem-in-Schema/m-p/2384407#M4922</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-05-27T14:44:02Z</dc:date>
    </item>
    <item>
      <title>Re: Turkish Character Problem in Schema</title>
      <link>https://community.qlik.com/t5/Installing-and-Upgrading/Turkish-Character-Problem-in-Schema/m-p/2384408#M4923</link>
      <description>If you have a lot of files for which you need to create the schema, you can create a job to replace any special character from the header by the corresponding standard utf-8 character.</description>
      <pubDate>Sun, 28 May 2017 14:51:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Installing-and-Upgrading/Turkish-Character-Problem-in-Schema/m-p/2384408#M4923</guid>
      <dc:creator>TRF</dc:creator>
      <dc:date>2017-05-28T14:51:17Z</dc:date>
    </item>
  </channel>
</rss>

