Unicode and e-mail
From Freepedia
| Unicode |
|---|
| Encodings |
| UCS |
| Bi-directional text |
| BOM |
| Han unification |
| Unicode and HTML |
| Unicode and e-mail |
Many email clients are now able to use Unicode. However most do not send in Unicode by default, and few systems are likely to be set up with fonts capable of displaying the full range of Unicode characters.
HTML e-mail can use HTML entities to use characters from anywhere in Unicode even if the HTML source text for the email is in a legacy encoding. For details of this see Unicode and HTML. The rest of this article will deal with email messages where the actual raw text (whether HTML markup or plain text) is in an encoding that covers the whole of unicode.
As with all encodings apart from US-ASCII, when using Unicode text in email MIME must be used to specify that a Unicode transformation format is being used for the text. UTF-7, although sometimes considered deprecated, has an advantage over other Unicode encodings in that it does not require a transfer encoding to fit within the seven-bit limits of many legacy Internet mail servers. UTF-8 and UTF-16 on the other hand must be transfer encoded in base64 or quoted-printable to allow safe transmission across seven-bit mail servers (i.e., those that do not advertise 8BITMIME).
Contents |
Unicode in various mail clients
Evolution
View > Character Encoding > Unicode
Tools > Settings > Mail Preferences and Composer Preferences > Check default Character Encoding to Unicode
Mozilla Thunderbird
View > Character Encoding > Unicode
Tools > Options… > Fonts > Outgoing Mail / Incoming Mail (change to Unicode)
MS Outlook
Outlook supports sending mail in UTF-7 and UTF-8 but does not do so by default. When replying, Outlook uses the same encoding as the message it is replying to. All Unicode characters can be entered in the edit box, but ones not available in the selected encoding will be silently replaced (usually with a question mark: ?) when sending the message.
i.Scribe/InScribe
Scribe will display unicode with default settings. But you can override the charset specified in the headers by right clicking on the body and using the "Change Charset" menu to select a new charset. You can also configure prefered charsets for 8-bit text and us-ascii in the receive options. When sending a suitable legacy charset (8bit, e.g. iso-8859-?? or windows-????) is chosen automatically however if the message has a complicated script or a mixture of scripts utf-8 will be used by default. You can set a prefered legacy charset in the sending options panel to override the default charset choice. Characters not available in the current font will be substituted from another font installed on the system (if available).
