MBOX-Line: From slusarz at curecanti.org  Tue Jul 10 11:45:42 2012
To: imap-protocol@u.washington.edu
From: Michael M Slusarz <slusarz@curecanti.org>
Date: Fri Jun  8 12:34:48 2018
Subject: [Imap-protocol] Non-ASCII text in the human readable portion of
	a response
In-Reply-To: <5B2D87F5-EFFF-4225-BE4A-F4660CF8E964@apple.com>
References: <5B2D87F5-EFFF-4225-BE4A-F4660CF8E964@apple.com>
Message-ID: <20120710124542.Horde.DgHsC4F5lbhP-HhWuUbyDRA@bigworm.curecanti.org>

Quoting Ian Anderson <iana@apple.com>:

> How is one supposed to put non-ASCII text in the human readable  
> portion of a response?  Something like this.
>
> tag01 NO [ALERT] some non-ASCII text to show the user
>
> RFC 3501 is unclear on this, it would seem to indicate that this  
> part of the response is "text" which boils down to "any CHAR except  
> CR and LF".  But how are the bytes to be interpreted?  Are they  
> limited to ASCII?  Is there another standard that allows non-ASCII  
> bytes?

RFC 3501 is limited to US-ASCII response text.  To use UTF-8, you need  
the LANGUAGE extension: RFC 5255 (http://tools.ietf.org/html/rfc5255).

michael


