<?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 How does Splunk parse german Umlauts? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-does-Splunk-parse-german-Umlauts/m-p/366017#M107965</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;

&lt;P&gt;I've been confronted with the problem, that the case insensitive search command  &lt;CODE&gt;search&lt;/CODE&gt;, differentiates between ö / Ö, ä / Ä and ü / Ü. My question now is, how does splunk parse the german Umlauts exactly and will it support case insensitivity searches for these characters in the near future?&lt;/P&gt;

&lt;P&gt;I'm aware of the workaround using  &lt;CODE&gt;eval lower() / upper()&lt;/CODE&gt;, so this question is not about solving the issue, but trying to understand where the issue really originates from. &lt;/P&gt;

&lt;P&gt;Thanks in advance and best regards,&lt;BR /&gt;
Bojan&lt;/P&gt;</description>
    <pubDate>Wed, 04 Oct 2017 14:36:17 GMT</pubDate>
    <dc:creator>bojanisch</dc:creator>
    <dc:date>2017-10-04T14:36:17Z</dc:date>
    <item>
      <title>How does Splunk parse german Umlauts?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-does-Splunk-parse-german-Umlauts/m-p/366017#M107965</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;

&lt;P&gt;I've been confronted with the problem, that the case insensitive search command  &lt;CODE&gt;search&lt;/CODE&gt;, differentiates between ö / Ö, ä / Ä and ü / Ü. My question now is, how does splunk parse the german Umlauts exactly and will it support case insensitivity searches for these characters in the near future?&lt;/P&gt;

&lt;P&gt;I'm aware of the workaround using  &lt;CODE&gt;eval lower() / upper()&lt;/CODE&gt;, so this question is not about solving the issue, but trying to understand where the issue really originates from. &lt;/P&gt;

&lt;P&gt;Thanks in advance and best regards,&lt;BR /&gt;
Bojan&lt;/P&gt;</description>
      <pubDate>Wed, 04 Oct 2017 14:36:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-does-Splunk-parse-german-Umlauts/m-p/366017#M107965</guid>
      <dc:creator>bojanisch</dc:creator>
      <dc:date>2017-10-04T14:36:17Z</dc:date>
    </item>
    <item>
      <title>Re: How does Splunk parse german Umlauts?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-does-Splunk-parse-german-Umlauts/m-p/366018#M107966</link>
      <description>&lt;P&gt;There is an open issue being tracked for this problem  (that also affects other non-ASCII characters), but there is no current fix version due to backwards compatibility concerns. I suggest you open a support case to add your voice to getting this addressed.&lt;BR /&gt;
Sorry, I don't have a more promising answer for you at this point. Äusserst unbefriedigend... &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Oct 2017 22:30:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-does-Splunk-parse-german-Umlauts/m-p/366018#M107966</guid>
      <dc:creator>s2_splunk</dc:creator>
      <dc:date>2017-10-04T22:30:39Z</dc:date>
    </item>
  </channel>
</rss>

