Platform Internationalization

The infrastructure team did a 1 week spike to better understand the BI Platform deficiencies related to internationalization. The spike focused primarily on character encoding issues. Attached is a Power Point document summarizing our findings, see Platform Encoding Slides. As a result of this spike five distinct Codec scenarios were identified. They are:

• Service Response Encoding - The character encoding used by any any web service responses.
• Solution Encoding - The character encoding used when writing text file content (xactions, etc.) to the solution repository.
• Content Encoding - The character encoding used when writing text data to the content repository.
• Config Encoding - The character encoding used when writing text file content (xml files) contained within the solution system folder.
• File Upload Encoding - The encoding used when uploading CSV files used for user-defined data sources. 

Each of these encodings will be user configurable. How they are configured is yet to be determined. The default encoding for each will be as follows:

• Service Response Encoding - UTF-8
• Solution Encoding - The default Java encoding.
• Content Encoding - UTF-8
• Config Encoding - UTF-8
• File Upload Encoding - UTF-8