Skip to content

Commit e0656f3

Browse files
committed
More accurate documentation
1 parent a6a7664 commit e0656f3

File tree

1 file changed

+5
-11
lines changed

1 file changed

+5
-11
lines changed

lib/net/imap.rb

Lines changed: 5 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1931,20 +1931,14 @@ def uid_thread(algorithm, search_keys, charset)
19311931
# UTF-7}[::decode_utf7] for mailbox names, or RFC2047 encoded-words for
19321932
# message headers.
19331933
#
1934-
# *Note:* For now, strings with 8-bit characters are still _sent_ using
1935-
# "literal" syntax. A future update will change how commands send UTF-8
1936-
# strings when <tt>UTF8=ACCEPT</tt> is enabled. This update should be
1937-
# backward-compatible.
1938-
#
19391934
# *Note:* <em>A future update may set string encodings slightly
19401935
# differently</em>, e.g: "US-ASCII" when UTF-8 is not enabled, and "UTF-8"
19411936
# when it is. Currently, the encoding of strings sent as "quoted" or
1942-
# "text" will _always_ be "UTF-8", even when a 7-bit encoding is used
1943-
# (e.g. UTF-7, encoded-words, quoted-printable, base64). And currently,
1944-
# string "literals" sent by the server will always have an "ASCII-8BIT"
1945-
# (binary) encoding, even if they must contain UTF-8 data---although a
1946-
# server _should_ use "quoted" strings once <tt>UTF8=ACCEPT</tt> is
1947-
# enabled.
1937+
# "text" will _always_ be "UTF-8", even when only ASCII characters are
1938+
# used (e.g. "Subject: Agenda") And currently, string "literals" sent
1939+
# by the server will always have an "ASCII-8BIT" (binary)
1940+
# encoding, even if they generally contain UTF-8 data, if they are
1941+
# text at all.
19481942
#
19491943
# [<tt>"UTF8=ONLY"</tt> [RFC6855[https://tools.ietf.org/html/rfc6855]]]
19501944
#

0 commit comments

Comments
 (0)