
Published:Mon, 26 Oct 2009 05:43:52 GMT
It's not a secret: Most PUC students do not check their PUC email. According to the SGA, a survey was sent out last semester about NetMail usage, in which students overwhelmingly ......
Published:Mon, 26 Oct 2009 20:59:19 GMT
Long-winded iPhone e-mail authors can tap, tap away in a new, automatically expanding window when composing mail from Gmail.com.......
Published:Tue, 03 Nov 2009 00:10:26 GMT
The social fanatic's dream. That's the tag-line for the Cliq, a new smartphone built by Motorola – and T-Mobile is hoping it will be enough to pry a swath of young consumers awa......
Published:Tue, 03 Nov 2009 08:07:42 GMT
The outlook for the third attempt to use an online elections system for the Associated Students (A.S.) elections in the past three years is optimistic, but no one is willing to sa......
Published:Mon, 02 Nov 2009 19:35:54 GMT
'Stikk' to your commitments By Erin Pheil special to the daily Truly Helpful Site of the Week: Stickk.com I learned about this gem of a site while reading the book Nudge by Richar......
Many e-Mail clients now offer some support for Unicode in e-mail bodies. Most do not send in Unicode by default, as the reader client might not support it, but as time passes, more and more systems are likely to be set up with fonts capable of displaying the full range of Unicode characters (or at least the set likely to be of interest to the user).
To use Unicode in e-mail subject lines and e-mail addresses two different standards need to be used to retrofit the handling of non-ASCII data to the originally ASCII-only e-mail protocol:
- RFC 2047 provides support for encoding non-ASCII values such as real names and subject lines in e-mail headers
- RFC 3490 provides support for encoding non-ASCII domain names in the Domain Name System
Unicode support in message bodies
As with all encodings apart from US-ASCII, when using Unicode text in e-mail, MIME must be used to specify that a Unicode transformation format is being used for the text. To use Unicode in e-mail headers, the Unicode text has to be encoded using a MIME "Encoded-Word" with a Unicode encoding as the charset.
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).
Some document formats, such as HTML, PostScript and Rich Text Format can use 7 bit codes for Unicode characters and can thus be sent without using any special e-mail encodings. E.g. HTML e-mail can use HTML entities to use characters from anywhere in Unicode even if the HTML source text for the e-mail is in a legacy encoding (e.g. 7-bit ASCII). For details of this see Unicode and HTML. The rest of this article deals with e-mail messages where the actual raw text (whether markup or plain text) is in an encoding that covers the whole of Unicode.
|
Comments submitted from other visitors |
More posts, Page # :

