Chris Kief wrote:
> I received a comment from a client the other day stating that the plain
> text email generated by their site (using cfmail) no longer looks like
> plain text when they get it (this is after an upgrade to CFMX). Huh???
>
> After digging into things a bit, I found that cfmail now uses
> Content-Type: text/plain; charset=UTF-8 for plain text emails. CF5 used
> Content-Type: text/plain; charset="us-ascii". When the email is viewed
> in Outlook, the encoding causes it to render a bit differently:
>
> UTF-8: http://www.riseinteractive.com/UTF-8.gif
> us-ascii: http://www.riseinteractive.com/us-ascii.gif
Looks like the default font that is set by the end user is not available
in UTF-8, only US_ASCII. I would say the problem is his lack of
understanding of the software he is actually using :)
> Adding the following solved the issue:
> <cfmailparam name="MIME-Version" value="1.0" />
> <cfmailparam name="Content-Type" value="text/plain; charset=us-ascii" />
>
> This leads me to the question - Is there a reason to leave it as UTF-8
> encoding? Or can I switch the charset to us-ascii and not worry about
> it?
<quote>
In other cases, like E-mail or stored data, there is no such
communication, and the best one can do is to make sure the charset is
clearly identified with the stored data, and choosing a charset that
is as widely known as possible.
</quote> RFC 2277, Charset Policy
So as long as the email you are sending only contains characters from
US-ASCII you should go for US-ASCII.
Jochem
______________________________________________________________________
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
