-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The export of Chinese data become messy code #8598
Comments
Could you provide an example data set or steps to reproduce? |
@Bargs Thanks for your attention. |
@LeeDr you looked into an issue like this before right? Didn't it end up being an issue with the encoding format excel tried by default or something like that? |
Here's my note from https://discuss.elastic.co/t/resolved-korean-text-is-broken-when-open-the-exported-csv-with-excel/53436/4 Instead of just clicking the csv to open with Excel, |
I don't have excel myself but from some quick googling it doesn't seem like excel handles any Unicode format well. http://stackoverflow.com/questions/6588068/which-encoding-opens-csv-files-correctly-with-excel-on-both-mac-and-windows If you can find a format that works well though, we'd be happy to look into implementing it. Otherwise, perhaps we could st least add some help text with Lee's instructions on importing. |
Here's an article with a lot of comments describing that if you put a UTF8 Byte-Order Mark (BOM) of I did some testing and think we should be adding the BOM when we write CSV export files from Kibana. I created this new issue so I'll close this one; |
Awesome detail, thanks @LeeDr |
Kibana version: 4.5.4
I export the chinese data by the raw or formatted link. but the chinese become messy code.
The text was updated successfully, but these errors were encountered: