<?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: How to print unicode as unicode? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288333#M55105</link>
    <description>&lt;P&gt;Hi @wegscd!&lt;BR /&gt;
It affects parsing.&lt;/P&gt;</description>
    <pubDate>Mon, 22 Jan 2018 05:34:33 GMT</pubDate>
    <dc:creator>MousumiChowdhur</dc:creator>
    <dc:date>2018-01-22T05:34:33Z</dc:date>
    <item>
      <title>How to print unicode as unicode?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288328#M55100</link>
      <description>&lt;P&gt;I have a JSON data source with data like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;{"download.doc_title": "GCP-7 R\u00f3znorodnosc, R\u00f3wne Szanse Oraz Szacunek W Miejscu Pracy.pdf"}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;If I look at the event syntax highlighted, it renders as I would expect:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;{   [-] 
     download.doc_title:     GCP-7 Róznorodnosc, Równe Szanse Oraz Szacunek W Miejscu Pracy.pdf   
}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;...but when I run any reports against, it shows up in the browser with the unicode escapes, instead of the unicode characters:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;searchcriteria&amp;gt; | table download.doc_title
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;shows&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;GCP-7 R\u00f3znorodnosc, R\u00f3wne Szanse Oraz Szacunek W Miejscu Pracy.pdf
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;how do I get it to show the Polish rendition?&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;GCP-7 Róznorodnosc, Równe Szanse Oraz Szacunek W Miejscu Pracy.pdf
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 04 Jan 2018 22:05:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288328#M55100</guid>
      <dc:creator>wegscd</dc:creator>
      <dc:date>2018-01-04T22:05:24Z</dc:date>
    </item>
    <item>
      <title>Re: How to print unicode as unicode?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288329#M55101</link>
      <description>&lt;P&gt;Hi!! Kindly refer to the link below:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/6.6.3/Data/Configurecharactersetencoding"&gt;https://docs.splunk.com/Documentation/SplunkCloud/6.6.3/Data/Configurecharactersetencoding&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 09:50:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288329#M55101</guid>
      <dc:creator>MousumiChowdhur</dc:creator>
      <dc:date>2018-01-05T09:50:45Z</dc:date>
    </item>
    <item>
      <title>Re: How to print unicode as unicode?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288330#M55102</link>
      <description>&lt;P&gt;Please set &lt;CODE&gt;CHARSET = AUTO&lt;/CODE&gt; in your props.conf&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 10:10:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288330#M55102</guid>
      <dc:creator>MousumiChowdhur</dc:creator>
      <dc:date>2018-01-05T10:10:05Z</dc:date>
    </item>
    <item>
      <title>Re: How to print unicode as unicode?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288331#M55103</link>
      <description>&lt;P&gt;The data is apparently being parsed correctly (remember, it displays correctly when syntax is highlighted). Will charset = auto affect parsing or display?&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 13:39:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288331#M55103</guid>
      <dc:creator>wegscd</dc:creator>
      <dc:date>2018-01-05T13:39:56Z</dc:date>
    </item>
    <item>
      <title>Re: How to print unicode as unicode?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288332#M55104</link>
      <description>&lt;P&gt;Similar issue at &lt;A href="https://answers.splunk.com/answers/555324/best-practice-for-dealing-with-unicode-codepoints.html"&gt;Best practice for dealing with Unicode codepoints in Splunk ?&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;But not much help there...&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 16:07:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288332#M55104</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2018-01-05T16:07:33Z</dc:date>
    </item>
    <item>
      <title>Re: How to print unicode as unicode?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288333#M55105</link>
      <description>&lt;P&gt;Hi @wegscd!&lt;BR /&gt;
It affects parsing.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jan 2018 05:34:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288333#M55105</guid>
      <dc:creator>MousumiChowdhur</dc:creator>
      <dc:date>2018-01-22T05:34:33Z</dc:date>
    </item>
    <item>
      <title>Re: How to print unicode as unicode?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288334#M55106</link>
      <description>&lt;P&gt;The data has been parsed correctly. This is a display side issue.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jan 2018 13:35:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-print-unicode-as-unicode/m-p/288334#M55106</guid>
      <dc:creator>wegscd</dc:creator>
      <dc:date>2018-01-22T13:35:28Z</dc:date>
    </item>
  </channel>
</rss>

