Sample code for 30+ languages & platforms
PowerBuilder

Write utf-8 CSV Compatible with Excel

See more CSV Examples

A CSV containing non-English characters that is saved using the utf-8 character encoding must include a BOM (also known as a preamble) if it is to be correctly loaded into Excel. See https://en.wikipedia.org/wiki/Byte_order_mark

This example shows how to save the CSV to a file using utf-8 with a BOM.

Note: This example requires Chilkat v9.5.0.93 or later.

Chilkat PowerBuilder Downloads

PowerBuilder
integer li_rc
integer li_Success
oleobject loo_Csv

li_Success = 0

// This example program loads a file (japanese.csv)
// that contains this content:
// 
// year,color,country,food
// 2001,red,France,cheese
// 2005,blue,"United States",hamburger
// 2008,green,Italy,pasta
// 1998,orange,Japan,sushi
// 2010,silver,"太志","森田"
// 

loo_Csv = create oleobject
li_rc = loo_Csv.ConnectToNewObject("Chilkat.Csv")
if li_rc < 0 then
    destroy loo_Csv
    MessageBox("Error","Connecting to COM object failed")
    return
end if
loo_Csv.HasColumnNames = 1
li_Success = loo_Csv.LoadFile2("qa_data/csv/test.csv","utf-8")
if li_Success <> 1 then
    Write-Debug loo_Csv.LastErrorText
    destroy loo_Csv
    return
end if

// To save the CSV using utf-8 with a BOM/preamble, 
// add "EMIT_BOM" to the UncommonOptions.
// (This feature was added in Chilkat v9.5.0.93)

loo_Csv.UncommonOptions = "EMIT_BOM"
li_Success = loo_Csv.SaveFile2("qa_output/test.csv","utf-8")
if li_Success <> 1 then
    Write-Debug loo_Csv.LastErrorText
    destroy loo_Csv
    return
end if

Write-Debug "OK, try to load the CSV in Excel to see if the non-English chars are correct."


destroy loo_Csv