Bug #5238

Use UTF-8 for file reading and writing

Added by ben leinfelder almost 12 years ago. Updated over 9 years ago.

morpho - general
Target version:
Start date:
Due date:
% Done:


Estimated time:


Rather than rely on the "default" character encoding used on individual platforms, Morpho should explicitly read and write text files using UTF-8 character encoding. When non-determinate encodings are used across different systems, special characters (accents, tildes, umlauts, Chinese, etc..) can become garbled and misinterpreted. Using the same encoding for all Morpho reading and writing will mitigate these encoding issues.
Note: this does not address character encoding issues that arise from copy/paste actions from other systems that use non-UTF-8 encoding (i.e. Word).

Related issues

Related to Morpho - Bug #6045: Morpho not correctly handling Chinese charactersIn Progress08/05/2013


#1 Updated by ben leinfelder almost 12 years ago

created a tag of the 1.8.1 code before committing the update to use UTF-8 across the board.

#2 Updated by Jim Regetz almost 12 years ago

I'll put in a vote for including an explicit encoding declaration in the EML docs that Morpho creates:

#3 Updated by ben leinfelder almost 12 years ago

This works:
Morpho now using UTF-8 for all reading and writing.
Additionally, special characters are not being escaped because we can encode them with UTF-8.

This does not:
Saving to Metacat (and the subsequent read) result in ????? for characters that should be, say, Chinese. This means (as I suspected) Metacat uses the default character encoding rather than explicitly using UTF-8.

#4 Updated by ben leinfelder over 9 years ago

This should be closed. UTF-8 is used exclusively in Morpho - especially important now that we have so much internationalization support

#5 Updated by Redmine Admin over 9 years ago

Original Bugzilla ID was 5238

Also available in: Atom PDF