<?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: encoding of exported CSV in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/How-to-fix-encoding-of-exported-CSV/m-p/756046#M12708</link>
    <description>&lt;P&gt;thank you this is still working although I edited the file in the pyton3.9 instead of 3.7&lt;/P&gt;&lt;P&gt;worked like a charm, appreciate it&lt;/P&gt;</description>
    <pubDate>Tue, 02 Dec 2025 07:24:27 GMT</pubDate>
    <dc:creator>ahmed_ramsey</dc:creator>
    <dc:date>2025-12-02T07:24:27Z</dc:date>
    <item>
      <title>How to fix encoding of exported CSV?</title>
      <link>https://community.splunk.com/t5/Reporting/How-to-fix-encoding-of-exported-CSV/m-p/563958#M10943</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;
&lt;P&gt;I have produced a search, which formats events in a table with couple of columns. The data and column names use Cyrillic words and in the GUI these look just fine. However, when I try to export the table as CSV (via the "Export To" option) the data and column names are encoded incorrectly and are not readable.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there a setting which I can change so that this problem is fixed?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I've searched the other topics here in Communities, but didn't find an asnwer, e.g.:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.splunk.com/t5/Splunk-Search/Why-are-special-characters-replaced-with-UTF-8-after-exporting/m-p/448248" target="_blank" rel="noopener"&gt;https://community.splunk.com/t5/Splunk-Search/Why-are-special-characters-replaced-with-UTF-8-after-exporting/m-p/448248&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.splunk.com/t5/Getting-Data-In/Korean-character-is-broken-when-I-export-the-query-results-in/m-p/180307" target="_blank" rel="noopener"&gt;https://community.splunk.com/t5/Getting-Data-In/Korean-character-is-broken-when-I-export-the-query-results-in/m-p/180307&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any help is appreciated,&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 22 Mar 2022 18:15:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/How-to-fix-encoding-of-exported-CSV/m-p/563958#M10943</guid>
      <dc:creator>vanvan</dc:creator>
      <dc:date>2022-03-22T18:15:31Z</dc:date>
    </item>
    <item>
      <title>Re: encoding of exported CSV</title>
      <link>https://community.splunk.com/t5/Reporting/How-to-fix-encoding-of-exported-CSV/m-p/564254#M10950</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/106176"&gt;@vanvan&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;If you see the exported CSV file readable in Notepad++/Sublime&amp;nbsp;but in Excel, below fix should work for you. Excel needs BOM characters at the beginning of file to understand UTF8.&lt;/P&gt;&lt;P&gt;Please update readall function as below and restart Splunk service. This is for Splunk 8.0 and later.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;$SPLUNK_HOME/lib/python3.7/site-packages/splunk/rest/__init__.py

def readall(self, blocksize=32768):
        """
        Returns a generator reading blocks of data from the response
        until all data has been read
        """
        response = self.response
        import codecs
        counter = 0;
        while True:
            data = response.read(blocksize)
            if not data:
                break
            if counter == 0:
                data = b"".join((codecs.BOM_UTF8, data))
                counter += 1
            yield data&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Aug 2021 04:24:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/How-to-fix-encoding-of-exported-CSV/m-p/564254#M10950</guid>
      <dc:creator>scelikok</dc:creator>
      <dc:date>2021-08-23T04:24:21Z</dc:date>
    </item>
    <item>
      <title>Re: encoding of exported CSV</title>
      <link>https://community.splunk.com/t5/Reporting/How-to-fix-encoding-of-exported-CSV/m-p/564256#M10951</link>
      <description>&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;This is interesting, I'll try it.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Aug 2021 04:50:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/How-to-fix-encoding-of-exported-CSV/m-p/564256#M10951</guid>
      <dc:creator>vanvan</dc:creator>
      <dc:date>2021-08-23T04:50:08Z</dc:date>
    </item>
    <item>
      <title>Re: encoding of exported CSV</title>
      <link>https://community.splunk.com/t5/Reporting/How-to-fix-encoding-of-exported-CSV/m-p/590228#M11288</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/206061"&gt;@scelikok&lt;/a&gt;,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tested the solution you provided in your post and it worked for me. Thank you for the time you spent on researching the matter. I saved me a lot of time.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I appreciate your willing ness to help. Have a great day.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ivan&lt;/P&gt;</description>
      <pubDate>Tue, 22 Mar 2022 14:43:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/How-to-fix-encoding-of-exported-CSV/m-p/590228#M11288</guid>
      <dc:creator>ivan_dzhantov</dc:creator>
      <dc:date>2022-03-22T14:43:39Z</dc:date>
    </item>
    <item>
      <title>Re: encoding of exported CSV</title>
      <link>https://community.splunk.com/t5/Reporting/How-to-fix-encoding-of-exported-CSV/m-p/756046#M12708</link>
      <description>&lt;P&gt;thank you this is still working although I edited the file in the pyton3.9 instead of 3.7&lt;/P&gt;&lt;P&gt;worked like a charm, appreciate it&lt;/P&gt;</description>
      <pubDate>Tue, 02 Dec 2025 07:24:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/How-to-fix-encoding-of-exported-CSV/m-p/756046#M12708</guid>
      <dc:creator>ahmed_ramsey</dc:creator>
      <dc:date>2025-12-02T07:24:27Z</dc:date>
    </item>
  </channel>
</rss>

