000029856 - Non-ASCII characters in the CSV output do not show correctly.

Document created by RSA Customer Support Employee on Jun 14, 2016•Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000029856
Applies ToRSA Product Set: Security Analytics
RSA Version/Condition: 10.3.x, 10.4.0, 10.4.1
Platform: CentOS







 Detect languageAfrikaansAlbanianArabicArmenianAzerbaijaniBasqueBengaliBelarusianBulgarianCatalanChinese (Simp)Chinese (Trad)CroatianCzechDanishDutchEnglishEsperantoEstonianFilipinoFinnishFrenchGalicianGeorgianGermanGreekGujaratiHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKannadaKoreanLaoLatinLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishTamilTeluguThaiTurkishUkrainianUrduVietnameseWelshYiddish
  
 

   		AfrikaansAlbanianArabicArmenianAzerbaijaniBasqueBengaliBelarusianBulgarianCatalanChinese (Simp)Chinese (Trad)CroatianCzechDanishDutchEnglishEsperantoEstonianFilipinoFinnishFrenchGalicianGeorgianGermanGreekGujaratiHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKannadaKoreanLaoLatinLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishTamilTeluguThaiTurkishUkrainianUrduVietnameseWelshYiddish 
  
 

  
  
 

  
  
 

  
 

  
  
 

   		 
  
 

  



 

 

Text-to-speech function is limited to 100 characters

 



IssueWhen running a report, non-ASCII characters in the CSV output (e.g Hebrew) do not show correctly. 
The reporting engine of SA produces a valid CSV file encoded in UTF-8 when the output data contains non-ASCII characters.
Although the Unicode Standard does not require or even recommend to use the byte order mark (BOM) in UTF-8 there is a common problem where Excel opens CSV files as ASCII because it uses BOM to detect that the stream is encoded in UTF-8. 
Resolution
As a workaround you can either:

 

a) convert a file to UTF-8 with BOM using any available tool or a script  (e.g. python)

 

or 

 

b) import a CSV file using the following steps: 

 

1. Open Excel.
2. Import the data using Data -> Get External Data from Text.
3. Select the file type of "csv" and browse to your file.
4. In the import wizard change the File_Origin to "65001 UTF" (or choose correct language character identifier). 
5. Change the Delimiter to comma. 
6. Select where to import to and press Finish.
 
NotesSATCE-840 - RFE for the support of CSV encoded in UTF-8 with BOM 

Attachments

    Outcomes