The built in text edit application has a 'Plain text encoding' option in the Save as... The standard Gnome Text Editor defaults to UTF-8 and has character set options when loading and saving.Our goal is to promote usage and support of the UTF-8 encoding and to convince that it should be the default choice of encoding for storing text strings in memory or on disk, for communication and all other uses.
(The notable exception to this is probably Notepad on Windows.) You may save a file using Notepad (sometimes called "Editor") as UTF-8 but not with Wordpad.
In 1996, the UTF-16 encoding was created so existing systems would be able to work with non-16-bit characters.
This effectively nullified the rationale behind choosing 16-bit encoding in the first place, namely being a fixed-width encoding.
We see no particular reason to favor Unicode code points over Unicode grapheme clusters, code units or perhaps even words in a language for that.
On the other hand, seeing UTF-8 code units (bytes) as a basic unit of text seems particularly useful for many tasks, such as parsing commonly used textual data formats.
For instance, a file copy utility should not be written differently to support non-English file names.
In this manifesto, we will also explain what a programmer should be doing if they do not want to dive into all complexities of Unicode and do not really care about what’s inside the string.
In particular, we believe that the very popular UTF-16 encoding (often mistakenly referred to as ‘widechar’ or simply ‘Unicode’ in the Windows world) has no place in library APIs except for specialized text processing libraries, e.g. This document also recommends choosing UTF-8 for internal string representation in Windows applications, despite the fact that this standard is less popular there, both due to historical reasons and the lack of native UTF-8 support by the API.
We believe that, even on this platform, the following arguments outweigh the lack of native support.
Download the "Complete package, except source" and run the setup program. Run from the command prompt (Start - cmd) and follow the instructions as above.
The conversion may also be done by using Cygwin, a Linux-like environment for Windows, and excecuting the iconv command in that environment.
We believe that our approach improves performance, reduces complexity of software and helps prevent many Unicode-related bugs.