In a message dated 2001-07-11 15:03:27 Pacific Daylight Time,
[EMAIL PROTECTED] writes:
> One exception to this should be US-ASCII because not only the repertoire
> of US-ASCII is a subset of the repertoire of UTF-8 but also the
> representation of all characters in US-ASCII is identical in UTF-8.
> A smart mail client would notice that all characters
> are in US-ASCII repertoire and label outgoing messages as in
> US-ASCII EVEN if it's configured to label outgoing messages
> in UTF-8
[...]
I thought this might even be enshrined in an RFC. It certainly makes sense.
If you are using a mailer that sends CP1252 down the wire (not that this is a
good idea, but some mailers do this), the mailer should examine the message
and if it only contains US-ASCII characters, the message should be tagged as
US-ASCII. Otherwise, if it only contains ISO 8859-1, it should be tagged as
ISO 8859-1. Only if it actually contains CP1252 characters, like smart
quotes or long dashes, should it be tagged as CP1252. As Jungshik observed,
the same goes for UTF-8.
-Doug Ewell
Fullerton, California
