[ 
https://issues.apache.org/jira/browse/KYLIN-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817161#comment-16817161
 ] 

ASF GitHub Bot commented on KYLIN-3939:
---------------------------------------

zhaojintaozhao commented on pull request #602: KYLIN-3939 add BOM 
character,slove the bug that it shows Chinese garb…
URL: https://github.com/apache/kylin/pull/602
 
 
   I find that if i open csv file using "notepad++", the Chinese characters are 
displayed normally. Then I convert this file to "UTF-8-BOM", then save this 
file. Then I open csv file using excel and the Chinese characters are displayed 
normally.
   Then I add BOM identifier to the query result to be output in 
"QueryController.java",I can open csv files usring excel and it displays 
normally. The system work fine after this change.
   This commit just fix this bug.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Open csv files  from query exported, the  Chinese characters are garbled
> ------------------------------------------------------------------------
>
>                 Key: KYLIN-3939
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3939
>             Project: Kylin
>          Issue Type: Bug
>          Components: REST Service
>    Affects Versions: v2.5.2
>            Reporter: zhao jintao
>            Assignee: zhao jintao
>            Priority: Minor
>
> Hi team;
> I query sql in kylin portal and  then press "Export" button to download the 
> result; the result is  csv files. I open the csv file using excel to get the 
> query results.
>  But I find that if the result has Chinese characters, the excel will show 
> Chinese characters garbled. 
>  Does any one face this problem?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to