Translation CSV Files and Excel ... (UTF8 vs UTF16)

Questions and information about Crank Software's Storyboard Designer

Moderator: jamiev

Translation CSV Files and Excel ... (UTF8 vs UTF16)

Postby thomas » Mon Oct 24, 2016 12:09 pm


One of the issues that comes up from time to time is the fact that all string content in Storyboard is UTF-8 (a good thing) so that we can universally support internationalized text.
[For more details on UTF-8 encoding and what it is visit:]

Our translation sample demonstrates how we provide a simple mapping of Storyboard variables to language content in a single comma separated value (CSV) text file. The content of these CSV file is also UTF-8 encoded so that whatever text content you want to use, it can be readily represented.

The challenge comes when you select to edit this CSV file with your local spreadsheet editor. The most popular spreadsheet is going to be Excel. Unfortunately, Excel does not save it's CSV files as UTF-8 encoded text, but rather UTF-16 encoded text. This is a well know 'deficiency' (lack of feature?) of Excel and it can be worked around by writing your own export macros (VBA can write UTF-8 encoded text just fine) or by using a different spreadsheet program or by editing the CSV file with the Storyboard text editor (which uses UTF8 encoding by default).

Alternatively, if you are stuck with using Excel, you can see the conversion hoops that others go through to get Excel two export UTF-8 text.
* ... om%20excel

We are working on a UTF-16 file reading module for Lua, but this seems like an un-necessary runtime cost for translated text when a bit of pre-processing to get the right content and format should be easy enough to do.

Posts: 135
Joined: Mon Nov 02, 2009 4:32 pm
Location: Ottawa

Return to Storyboard Designer

Who is online

Users browsing this forum: Bing [Bot] and 1 guest