MBOX-Line: From dave at cridland.net  Fri May 27 00:51:40 2011
To: imap-protocol@u.washington.edu
From: Dave Cridland <dave@cridland.net>
Date: Fri Jun  8 12:34:46 2018
Subject: [Imap-protocol] History question.
In-Reply-To: <alpine.OSX.2.00.1105262111590.973@hsinghsing.panda.com>
References: <4DDEA412.6030305@aol.com> <4DDEDDD6.1040507@logicprobe.org>
	<alpine.BSO.2.00.1105261628370.892@morgaine.smi.sendmail.com>
	<2CB073A1-B421-4CFB-AE30-B17005C876A0@iki.fi>
	<alpine.OSX.2.00.1105261724000.973@hsinghsing.panda.com>
	<4DDF06A9.2050608@logicprobe.org> <4DDF1140.3030101@verizon.net>
	<alpine.OSX.2.00.1105262111590.973@hsinghsing.panda.com>
Message-ID: <3054.1306482700.081469@puncture>

On Fri May 27 05:19:45 2011, Mark Crispin wrote:
> On Thu, 26 May 2011, Joshua Cranmer wrote:
>> I have been told that there are some devices capable of reading  
>> email
>> that do not support UTF-8. Not as in "they can't display it  
>> correctly"
>> but as in "they can't decode it properly even when explicitly told  
>> this
>> text is UTF-8."
> 
> There is no excuse for a lack of UTF-8 support in any email device
> produced after 1996, and especially after the publication of RFC  
> 2130 in
> 1997.
> 
> Sadly, there is no enforcement.

But who cares?

If a device only understands ASCII, send them UTF-8 anyway and the  
worst that can happen is that a fully non-ASCII message is  
unreadable, which it would be anyway.

Of course, if these devices only understand one of the non-ASCII  
charsets (ie, those which are not ASCII subset compatible), then  
you're doomed anyway.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

