# \[Resolved\] Korean text is broken when open the exported CSV with Excel

**URL:** <https://discuss.elastic.co/t/resolved-korean-text-is-broken-when-open-the-exported-csv-with-excel/53436>\
**Category:** Kibana\
**Created:** [June 21, 2016, 7:18am UTC](https://discuss.elastic.co/t/resolved-korean-text-is-broken-when-open-the-exported-csv-with-excel/53436 "2016-06-21T07:18:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jungmi\_Yoo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jungmi_yoo/32/33449_2.png) [@Jungmi\_Yoo](https://discuss.elastic.co/u/Jungmi_Yoo)\
**Post date:** [June 21, 2016, 7:18am UTC](https://discuss.elastic.co/t/resolved-korean-text-is-broken-when-open-the-exported-csv-with-excel/53436/1 "2016-06-21T07:18:48Z")

</div>

I tried to open my CSV that i exported on Kibana Dashbord on Excel.  
However it was broken like this. It looks BOM header issue. So I re-stored it file with "UTF-8 BOM" on Sublime Text.  
But it is still broken. My OS is MAC. So i tried to save it on Windows Notepade. Then it is working, not broken.

I want to know that Kibana has a fixing plan this export CSV isssue?

 ![](https://us1.discourse-cdn.com/elastic/original/2X/e/e95eb71c67564e35a50c5cb6b2c8479700ec1433.png)

---

<div class="post-metadata">

**Author:** ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)\
**Post date:** [June 21, 2016, 2:31pm UTC](https://discuss.elastic.co/t/resolved-korean-text-is-broken-when-open-the-exported-csv-with-excel/53436/2 "2016-06-21T14:31:11Z")

</div>

Hi @Jungmi_Yoo, I tried to reproduce the issue but I'm not having success, I might need some more information from you.

- What version of Kibana/Elasticsearch are you using?
- Can you provide relevant steps to reproduce? A sample document or two that demonstrate the problem would be great.
- What platform are you using Excel on? I don't have Excel, but I was able to import into Apple's Numbers without issue. Is Excel the only application that has issues with the file?

---

<div class="post-metadata">

**Author:** ![Jungmi\_Yoo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jungmi_yoo/32/33449_2.png) [@Jungmi\_Yoo](https://discuss.elastic.co/u/Jungmi_Yoo)\
**Post date:** [June 22, 2016, 5:17am UTC](https://discuss.elastic.co/t/resolved-korean-text-is-broken-when-open-the-exported-csv-with-excel/53436/3 "2016-06-22T05:17:44Z")

</div>

Here are my answers.

- What version of Kibana/Elasticsearch are you using?  
==\> Kibana : 4.5.1 Elasticsearch : 2.3.3

- Can you provide relevant steps to reproduce? A sample document or two that demonstrate the problem would be great.  
==\> reproduce steps

- What platform are you using Excel on? I don't have Excel, but I was able to import into Apple's Numbers without issue. Is Excel the only application that has issues with the file?  
==\> this issue is raising on both platform MAC OS and Windows. when i opne the exported CSV file is fine. But this issue only produced when I open on EXCEL.

Therefore I'm thinking it looks BOM (Byte Order Mark) issue related with Microsoft.

Thanks,

---

<div class="post-metadata">

**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\
**Post date:** [June 22, 2016, 2:54pm UTC](https://discuss.elastic.co/t/resolved-korean-text-is-broken-when-open-the-exported-csv-with-excel/53436/4 "2016-06-22T14:54:19Z")

</div>

Hi Jungmi,

I tested on Windows and I see that the csv files Kibana exports are UTF-8 encoding.

For test data, I loaded this one doc with some unicode characters;

```
{
  "accounts_info": {
    "server": "localhost",
    "type": "£¥₧ƒ¢֍֎۞߷ೱೲ๏ᐂᚙ⏰⏳☸"
  }
}

```

After I loaded it I realized that the standard analyzer parsed that string on things it considered currency and maybe others into 3 separate terms. I'm not going to worry about that.

So here's what I have in my data table visualization;

 ![](https://us1.discourse-cdn.com/elastic/original/2X/a/ae544f1fdc5222782fb90de419f6fa0e06f2a2cd.png)

When I export that I get this;

```
"accounts_info.type: Descending",Count
"ƒ",1
"ೱೲ",1
"ᐂᚙ",1

```

If I just click on the csv file and select "Open with Excel" (Excel 2016) I get garbage;  
 ![](https://us1.discourse-cdn.com/elastic/original/2X/7/764d18cd03351ee98f1405c4573df4c1cc64697b.png)

But if I open Excel and use `Data > Get External Data > From File` and check that the  
`File origin` is `65001: Unicode (UTF-8)` (mine was already set that way).  
Then I can see that the data is the same as I saw in Kibana (and the same as the document I loaded except for the analyzing);

![](https://us1.discourse-cdn.com/elastic/original/2X/5/5593f5b63d2192afcb0063ec116a0c35d12e07d9.png)

![](https://us1.discourse-cdn.com/elastic/original/2X/2/2463cc9a175796d510ce1b797d0bda994c166d67.png)

So please try to load your csv into Excel by this `Get External Data` method and see if that works better.

Regards,  
Lee

---

<div class="post-metadata">

**Author:** ![Jungmi\_Yoo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jungmi_yoo/32/33449_2.png) [@Jungmi\_Yoo](https://discuss.elastic.co/u/Jungmi_Yoo)\
**Post date:** [June 23, 2016, 1:48am UTC](https://discuss.elastic.co/t/resolved-korean-text-is-broken-when-open-the-exported-csv-with-excel/53436/5 "2016-06-23T01:48:37Z")

</div>

Thank you so much Lee.  
This issue is resolved on Winodw. on Mac, i can use the Numbers.( Excel:mac 2011 is not works.)

Thanks again,  
Jungmi

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:49pm UTC](https://discuss.elastic.co/t/resolved-korean-text-is-broken-when-open-the-exported-csv-with-excel/53436/6 "2017-07-06T13:49:30Z")

</div>