It's all about the answers!

Ask a question

Exported CSV from DNG contains garbled Japanese characters


Taro Misaki (145617) | asked Aug 07 '15, 2:10 a.m.
Hi,
I exported a list of artifacts to a CSV file. The CSV file contains Japanese characters in both heading and primary texts.
When I double clicked and opened it in an Excel. The Japanese characters are garbled.
How can I make DNG to export to CSV so that the Japanese characters won't be garbled when opened in Excel?

Accepted answer


permanent link
Howard Hsiao (5.5k17) | answered Aug 07 '15, 2:17 a.m.
JAZZ DEVELOPER
Most probable cause:
When DNG exports artifacts to CSV file, it exports in UTF-8.
When the exported CSV is opened in Excel, it is opened in ANSI encoding, hence Japanese characters cannot be displayed correctly.
In Excel, you cannot open a CSV in UTF-8 by just doing the normal File > Open.

Test probable cause:
Use Excel to open CSV in UTF-8 format and see if Japanese characters can be displayed properly

Method 1: (faster)
1. open the exported CSV in Notepad
2. save it straightaway without editing
3. double click the CSV to open it in Excel in UTF-8
* the save without editing in Notepad actually prepends the CSV file with UTF-8 BOM

Method 2: (need to have script engine/program installed)
1. Use script/program to inject UTF-8 BOM into CSV
2. double click the CSV to open it in Excel in UTF-8

Method 3: (too many steps!!)
1. click on Data on the menu
2. click on "From Text" in "Get External Data" section
3. open the CSV file
4. in Step 1 of Text Import Wizard, make sure "Unicode (UTF-8)" is selected
5. in Step 2 of Text Import Wizard, make sure "Comma" is selected as Delimiters
6. Click on Finish and select "New worksheet" to put the data

Think beyond fix:
This issue does not only apply to Japanese texts but also for all texts that are encoded in UTF-8 format.
Taro Misaki selected this answer as the correct answer

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.