As per Relevance of the word standard, we have this rfc below:
Network Working Group K.
Request for Comments: 2047 University of
Obsoletes: 1521, 1522, 1590 November 1996
Category: Standards
MIME (Multipurpose Internet Mail Extensions) Part Three
Message Header Extensions for Non-ASCII
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
STD 11, RFC 822, defines a message representation protocol
considerable detail about US-ASCII message headers, and leaves
message content, or message body, as flat US-ASCII text. This set
documents, collectively called the Multipurpose Internet
Extensions, or MIME, redefines the format of messages to allow
(1) textual message bodies in character sets other than US-ASCII
(2) an extensible set of different formats for non-textual
bodies
(3) multi-part message bodies,
(4) textual header information in character sets other than US-ASCII
These documents are based on earlier work documented in RFC 934,
11, and RFC 1049, but extends and revises them. Because RFC 822
so little about message bodies, these documents are
orthogonal to (rather than a revision of) RFC 822.
This particular document is the third document in the series.
describes extensions to RFC 822 to allow non-US-ASCII text data
Internet mail header fields
Moore Standards Track [Page 1]
RFC 2047 Message Header Extensions November 1996
Other documents in this series include
+ RFC 2045, which specifies the various headers used to
the structure of MIME messages
+ RFC 2046, which defines the general structure of the MIME
typing system and defines an initial set of media types
+ RFC 2048, which specifies various IANA registration
for MIME-related facilities,
+ RFC 2049, which describes MIME conformance criteria
provides some illustrative examples of MIME message formats
acknowledgements, and the bibliography
These documents are revisions of RFCs 1521, 1522, and 1590,
themselves were revisions of RFCs 1341 and 1342. An appendix in
2049 describes differences and changes from previous versions
1.
RFC 2045 describes a mechanism for denoting textual body parts
are coded in various character sets, as well as methods for
such body parts as sequences of printable US-ASCII characters.
memo describes similar techniques to allow the encoding of non-
text in various portions of a RFC 822 [2] message header, in a
which is unlikely to confuse existing message handling software
Like the encoding techniques described in RFC 2045, the
outlined here were designed to allow the use of non-ASCII
in message headers in a way which is unlikely to be disturbed by
quirks of existing Internet mail handling programs. In particular
some mail relaying programs are known to (a) delete some
header fields while retaining others, (b) rearrange the order
addresses in To or Cc fields, (c) rearrange the (vertical) order
header fields, and/or (d) "wrap" message headers at different
than those in the original message. In addition, some mail
programs are known to have difficulty correctly parsing
headers which, while legal according to RFC 822, make use
backslash-quoting to "hide" special characters such as "<", ",",
":", or which exploit other infrequently-used features of
specification
While it is unfortunate that these programs do not
interpret RFC 822 headers, to "break" these programs would
severe operational problems for the Internet mail system.
extensions described in this memo therefore do not rely on little
used features of RFC 822.
Moore Standards Track [Page 2]
RFC 2047 Message Header Extensions November 1996
Instead, certain sequences of "ordinary" printable ASCII
(known as "encoded-words") are reserved for use as encoded data.
syntax of encoded-words is such that they are unlikely
"accidentally" appear as normal text in message headers
Furthermore, the characters used in encoded-words are restricted
those which do not have special meanings in the context in which
encoded-word appears
Generally, an "encoded-word" is a sequence of printable
characters that begins with "=?", ends with "?=", and has two "?"s
between. It specifies a character set and an encoding method,
also includes the original text encoded as graphic ASCII characters
according to the rules for that encoding method
A mail composer that implements this specification will provide
means of inputting non-ASCII text in header fields, but
translate these fields (or appropriate portions of these fields)
encoded-words before inserting them into the message header
A mail reader that implements this specification will
encoded-words when they appear in certain portions of the
header. Instead of displaying the encoded-word "as is", it
reverse the encoding and display the original text in the
character set
This memo relies heavily on notation and terms defined RFC 822
RFC 2045. In particular, the syntax for the ABNF used in this
is defined in RFC 822, as well as many of the terminal or
symbols from RFC 822 are used in the grammar for the
extensions defined here. Among the symbols defined in RFC 822
referenced in this memo are: 'addr-spec', 'atom', 'CHAR', 'comment',
'CTLs', 'ctext', 'linear-white-space', 'phrase', 'quoted-pair'.
'quoted-string', 'SPACE', and 'word'. Successful implementation
this protocol extension requires careful attention to the RFC 822
definitions of these terms
When the term "ASCII" appears in this memo, it refers to the "7-
American Standard Code for Information Interchange", ANSI X3.4-1986.
The MIME charset name for this character set is "US-ASCII". When
specifically referring to the MIME charset name, this document
the term "ASCII", both for brevity and for consistency with RFC 822.
However, implementors are warned that the character set name must
spelled "US-ASCII" in MIME message and body part headers
Moore Standards Track [Page 3]
RFC 2047 Message Header Extensions November 1996
This memo specifies a protocol for the representation of non-
text in message headers. It specifically DOES NOT define
translation between "8-bit headers" and pure ASCII headers, nor
any such translation assumed to be possible
2. Syntax of encoded-
An 'encoded-word' is defined by the following ABNF grammar.
notation of RFC 822 is used, with the exception that white
characters MUST NOT appear between components of an 'encoded-word'.
encoded-word = "=?" charset "?" encoding "?" encoded-text "?="
charset = token ; see section 3
encoding = token ; see section 4
token = 1*
especials = "(" / ")" / "<" / ">" / "@" / "," / ";" / ":" / "
<"> / "/" / "[" / "]" / "?" / "." / "="
encoded-text = 1*printable ASCII character other than "?"
or SPACE
; (but see "Use of encoded-words in
; headers", section 5)
Both 'encoding' and 'charset' names are case-independent. Thus
charset name "ISO-8859-1" is equivalent to "iso-8859-1", and
encoding named "Q" may be spelled either "Q" or "q".
An 'encoded-word' may not be more than 75 characters long,
'charset', 'encoding', 'encoded-text', and delimiters. If it
desirable to encode more text than will fit in an 'encoded-word'
75 characters, multiple 'encoded-word's (separated by CRLF SPACE)
be used
While there is no limit to the length of a multiple-line
field, each line of a header field that contains one or
'encoded-word's is limited to 76 characters
The length restrictions are included both to ease
through internetwork mail gateways, and to impose a limit on
amount of lookahead a header parser must employ (while looking for
final ?= delimiter) before it can decide whether a token is
"encoded-word" or something else
Moore Standards Track [Page 4]
RFC 2047 Message Header Extensions November 1996
IMPORTANT: 'encoded-word's are designed to be recognized as 'atom'
by an RFC 822 parser. As a consequence, unencoded white
characters (such as SPACE and HTAB) are FORBIDDEN within
'encoded-word'. For example, the character
=?iso-8859-1?q?this is some text?=
would be parsed as four 'atom's, rather than as a single 'atom' (
an RFC 822 parser) or 'encoded-word' (by a parser which
'encoded-words'). The correct way to encode the string "this is
text" is to encode the SPACE characters as well, e.g
=?iso-8859-1?q?this=20is=20some=20text?=
The characters which may appear in 'encoded-text' are
restricted by the rules in section 5.
3. Character
The 'charset' portion of an 'encoded-word' specifies the
set associated with the unencoded text. A 'charset' can be any
the character set names allowed in an MIME "charset" parameter of
"text/plain" body part, or any character set name registered
IANA for use with the MIME text/plain content-type
Some character sets use code-switching techniques to switch
"ASCII mode" and other modes. If unencoded text in an 'encoded-word
contains a sequence which causes the charset interpreter to
out of ASCII mode, it MUST contain additional control codes such
ASCII mode is again selected at the end of the 'encoded-word'. (
rule applies separately to each 'encoded-word', including
'encoded-word's within a single header field.)
When there is a possibility of using more than one character set
represent the text in an 'encoded-word', and in the absence
private agreements between sender and recipients of a message, it
recommended that members of the ISO-8859-* series be used
preference to other character sets
4.
Initially, the legal values for "encoding" are "Q" and "B".
encodings are described below. The "Q" encoding is recommended
use when most of the characters to be encoded are in the
character set; otherwise, the "B" encoding should be used
Nevertheless, a mail reader which claims to recognize 'encoded-word'
MUST be able to accept either encoding for any character set which
supports
Moore Standards Track [Page 5]
RFC 2047 Message Header Extensions November 1996
Only a subset of the printable ASCII characters may be used
'encoded-text'. Space and tab characters are not allowed, so
the beginning and end of an 'encoded-word' are obvious. The "?"
character is used within an 'encoded-word' to separate the
portions of the 'encoded-word' from one another, and thus
appear in the 'encoded-text' portion. Other characters are
illegal in certain contexts. For example, an 'encoded-word' in
'phrase' preceding an address in a From header field may not
any of the "specials" defined in RFC 822. Finally, certain
characters are disallowed in some contexts, to ensure reliability
messages that pass through internetwork mail gateways
The "B" encoding automatically meets these requirements. The "Q
encoding allows a wide range of printable characters to be used
non-critical locations in the message header (e.g., Subject),
fewer characters available for use in other locations
4.1. The "B"
The "B" encoding is identical to the "BASE64" encoding defined by
2045.
4.2. The "Q"
The "Q" encoding is similar to the "Quoted-Printable" content
transfer-encoding defined in RFC 2045. It is designed to allow
containing mostly ASCII characters to be decipherable on an
terminal without decoding
(1) Any 8-bit value may be represented by a "=" followed by
hexadecimal digits. For example, if the character set in
were ISO-8859-1, the "=" character would thus be encoded
"=3D", and a SPACE by "=20". (Upper case should be used
hexadecimal digits "A" through "F".)
(2) The 8-bit hexadecimal value 20 (e.g., ISO-8859-1 SPACE) may
represented as "_" (underscore, ASCII 95.). (This character
not pass through some internetwork mail gateways, but its
will greatly enhance readability of "Q" encoded data with
readers that do not support this encoding.) Note that the "_"
always represents hexadecimal 20, even if the SPACE
occupies a different code position in the character set in use
(3) 8-bit values which correspond to printable ASCII characters
than "=", "?", and "_" (underscore), MAY be represented as
characters. (But see section 5 for restrictions.)
particular, SPACE and TAB MUST NOT be represented as
within encoded words
Moore Standards Track [Page 6]
RFC 2047 Message Header Extensions November 1996
5. Use of encoded-words in message
An 'encoded-word' may appear in a message header or body part
according to the following rules
(1) An 'encoded-word' may replace a 'text' token (as defined by RFC 822)
in any Subject or Comments header field, any extension
header field, or any MIME body part field for which the field
is defined as '*text'. An 'encoded-word' may also appear in
user-defined ("X-") message or body part header field
Ordinary ASCII text and 'encoded-word's may appear together in
same header field. However, an 'encoded-word' that appears in
header field defined as '*text' MUST be separated from any
'encoded-word' or 'text' by 'linear-white-space'.
(2) An 'encoded-word' may appear within a 'comment' delimited by "("
")", i.e., wherever a 'ctext' is allowed. More precisely, the
822 ABNF definition for 'comment' is amended as follows
comment = "(" *(ctext / quoted-pair / comment / encoded-word) ")"
A "Q"-encoded 'encoded-word' which appears in a 'comment' MUST
contain the characters "(", ")" or "
'encoded-word' that appears in a 'comment' MUST be separated
any adjacent 'encoded-word' or 'ctext' by 'linear-white-space'.
It is important to note that 'comment's are only recognized
"structured" field bodies. In fields whose bodies are defined
'*text', "(" and ")" are treated as ordinary characters rather
comment delimiters, and rule (1) of this section applies. (See
822, sections 3.1.2 and 3.1.3)
(3) As a replacement for a 'word' entity within a 'phrase', for example
one that precedes an address in a From, To, or Cc header. The
definition for 'phrase' from RFC 822 thus becomes
phrase = 1*( encoded-word / word )
In this case the set of characters that may be used in a "Q"-
'encoded-word' is restricted to:
letters, decimal digits, "!", "*", "+", "-", "/", "=", and "_"
(underscore, ASCII 95.)>. An 'encoded-word' that appears within
'phrase' MUST be separated from any adjacent 'word', 'text'
'special' by 'linear-white-space'.
Moore Standards Track [Page 7]
RFC 2047 Message Header Extensions November 1996
These are the ONLY locations where an 'encoded-word' may appear.
particular
+ An 'encoded-word' MUST NOT appear in any portion of an 'addr-spec'.
+ An 'encoded-word' MUST NOT appear within a 'quoted-string'.
+ An 'encoded-word' MUST NOT be used in a Received header field
+ An 'encoded-word' MUST NOT be used in parameter of a
Content-Type or Content-Disposition field, or in any
field body except within a 'comment' or 'phrase'.
The 'encoded-text' in an 'encoded-word' must be self-contained
'encoded-text' MUST NOT be continued from one 'encoded-word'
another. This implies that the 'encoded-text' portion of a "B
'encoded-word' will be a multiple of 4 characters long; for a "Q
'encoded-word', any "=" character that appears in the 'encoded-text
portion will be followed by two hexadecimal characters
Each 'encoded-word' MUST encode an integral number of octets.
'encoded-text' in each 'encoded-word' must be well-formed
to the encoding specified; the 'encoded-text' may not be continued
the next 'encoded-word'. (For example, "=?charset?Q?=?=
=?charset?Q?AB?=" would be illegal, because the two hex digits "AB
must follow the "=" in the same 'encoded-word'.)
Each 'encoded-word' MUST represent an integral number of characters
A multi-octet character may not be split across adjacent 'encoded
word's
Only printable and white space character data should be encoded
this scheme. However, since these encoding schemes allow
encoding of arbitrary octet values, mail readers that implement
decoding should also ensure that display of the decoded data on
recipient's terminal will not cause unwanted side-effects
Use of these methods to encode non-textual data (e.g., pictures
sounds) is not defined by this memo. Use of 'encoded-word's
represent strings of purely ASCII characters is allowed,
discouraged. In rare cases it may be necessary to encode
text that looks like an 'encoded-word'.
Moore Standards Track [Page 8]
RFC 2047 Message Header Extensions November 1996
6. Support of 'encoded-word's by mail
6.1. Recognition of 'encoded-word's in message
A mail reader must parse the message and body part headers
to the rules in RFC 822 to correctly recognize 'encoded-word's
'encoded-word's are to be recognized as follows
(1) Any message or body part header field defined as '*text', or
user-defined header field, should be parsed as follows:
at the start of the field-body and immediately following
occurrence of 'linear-white-space', each sequence of up to 75
printable characters (not containing any 'linear-white-space')
should be examined to see if it is an 'encoded-word' according
the syntax rules in section 2. Any other sequence of
characters should be treated as ordinary ASCII text
(2) Any header field not defined as '*text' should be
according to the syntax rules for that header field. However
any 'word' that appears within a 'phrase' should be treated as
'encoded-word' if it meets the syntax rules in section 2.
Otherwise it should be treated as an ordinary 'word'.
(3) Within a 'comment', any sequence of up to 75 printable
(not containing 'linear-white-space'), that meets the
rules in section 2, should be treated as an 'encoded-word'.
Otherwise it should be treated as normal comment text
(4) A MIME-Version header field is NOT required to be present
'encoded-word's to be interpreted according to
specification. One reason for this is that the mail reader
not expected to parse the entire message header before
lines that may contain 'encoded-word's
6.2. Display of 'encoded-word'
Any 'encoded-word's so recognized are decoded, and if possible,
resulting unencoded text is displayed in the original character set
NOTE: Decoding and display of encoded-words occurs *after*
structured field body is parsed into tokens. It is
possible to hide 'special' characters in encoded-words which,
displayed, will be indistinguishable from 'special' characters in
surrounding text. For this and other reasons, it is NOT
possible to translate a message header containing 'encoded-word's
an unencoded form which can be parsed by an RFC 822 mail reader
Moore Standards Track [Page 9]
RFC 2047 Message Header Extensions November 1996
When displaying a particular header field that contains
'encoded-word's, any 'linear-white-space' that separates a pair
adjacent 'encoded-word's is ignored. (This is to allow the use
multiple 'encoded-word's to represent long strings of unencoded text
without having to separate 'encoded-word's where spaces occur in
unencoded text.)
In the event other encodings are defined in the future, and the
reader does not support the encoding used, it may either (a)
the 'encoded-word' as ordinary text, or (b) substitute an
message indicating that the text could not be decoded
If the mail reader does not support the character set used, it
(a) display the 'encoded-word' as ordinary text (i.e., as it
in the header), (b) make a "best effort" to display using
characters as are available, or (c) substitute an appropriate
indicating that the decoded text could not be displayed
If the character set being used employs code-switching techniques
display of the encoded text implicitly begins in "ASCII mode".
addition, the mail reader must ensure that the output device is
again in "ASCII mode" after the 'encoded-word' is displayed
6.3. Mail reader handling of incorrectly formed 'encoded-word'
It is possible that an 'encoded-word' that is legal according to
syntax defined in section 2, is incorrectly formed according to
rules for the encoding being used. For example
(1) An 'encoded-word' which contains characters which are not
for a particular encoding (for example, a "-" in the "B
encoding, or a SPACE or HTAB in either the "B" or "Q" encoding),
is incorrectly formed
(2) Any 'encoded-word' which encodes a non-integral number
characters or octets is incorrectly formed
A mail reader need not attempt to display the text associated with
'encoded-word' that is incorrectly formed. However, a mail
MUST NOT prevent the display or handling of a message because
'encoded-word' is incorrectly formed
7.
A mail composing program claiming compliance with this
MUST ensure that any string of non-white-space printable
characters within a '*text' or '*ctext' that begins with "=?"
ends with "?=" be a valid 'encoded-word'. ("begins" means: at
Moore Standards Track [Page 10]
RFC 2047 Message Header Extensions November 1996
start of the field-body, immediately following 'linear-white-space',
or immediately following a "(" for an 'encoded-word' within '*ctext';
"ends" means: at the end of the field-body, immediately
'linear-white-space', or immediately preceding a ")" for
'encoded-word' within '*ctext'.) In addition, any 'word' within
'phrase' that begins with "=?" and ends with "?=" must be a
'encoded-word'.
A mail reading program claiming compliance with this
must be able to distinguish 'encoded-word's from 'text', 'ctext',
'word's, according to the rules in section 6, anytime they appear
appropriate places in message headers. It must support both the "B
and "Q" encodings for any character set which it supports.
program must be able to display the unencoded text if the
set is "US-ASCII". For the ISO-8859-* character sets, the
reading program must at least be able to display the characters
are also in the ASCII set
8.
The following are examples of message headers containing 'encoded
word's
From: =?US-ASCII?Q?Keith_Moore?=
To: =?ISO-8859-1?Q?Keld_J=F8rn_Simonsen?=
CC: =?ISO-8859-1?Q?Andr=E9?= Pirard
Subject: =?ISO-8859-1?B?SWYgeW91IGNhbiByZWFkIHRoaXMgeW8=?=
=?ISO-8859-2?B?dSB1bmRlcnN0YW5kIHRoZSBleGFtcGxlLg==?=
Note: In the first 'encoded-word' of the Subject field above,
last "=" at the end of the 'encoded-text' is necessary because
'encoded-word' must be self-contained (the "=" character completes
group of 4 base64 characters representing 2 octets). An
octet could have been encoded in the first 'encoded-word' (so
the encoded-word would contain an exact multiple of 3
octets), except that the second 'encoded-word' uses a
'charset' than the first one
From: =?ISO-8859-1?Q?Olle_J=E4rnefors?=
To: ietf-822@dimacs.rutgers.edu, ojarnef@admin.kth.
Subject: Time for ISO 10646?
To: Dave Crocker stanford.edu
Cc: ietf-822@dimacs.rutgers.edu, paf@comsol.
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?=
Subject: Re: RFC-HDR care and
Moore Standards Track [Page 11]
RFC 2047 Message Header Extensions November 1996
From: Nathaniel Borenstein
(=?iso-8859-8?b?7eXs+SDv4SDp7Oj08A==?=)
To: Greg Vaudreuil , Ned
, Keith Moore
Subject: Test of new header
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
The following examples illustrate how text containing 'encoded-word'
which appear in a structured field body. The rules are
different for fields defined as '*text' because "(" and ")" are
recognized as 'comment' delimiters. [Section 5, paragraph (1)].
In each of the following examples, if the same sequence were to
in a '*text' field, the "displayed as" form would NOT be treated
encoded words, but be identical to the "encoded form". This
because each of the encoded-words in the following examples
adjacent to a "(" or ")" character
encoded form displayed
---------------------------------------------------------------------
(=?ISO-8859-1?Q?a?=) (a
(=?ISO-8859-1?Q?a?= b) (a b
Within a 'comment', white space MUST appear between
'encoded-word' and surrounding text. [Section 5,
paragraph (2)]. However, white space is not needed
the initial "(" that begins the 'comment', and
'encoded-word'.
(=?ISO-8859-1?Q?a?= =?ISO-8859-1?Q?b?=) (ab
White space between adjacent 'encoded-word's is
displayed
(=?ISO-8859-1?Q?a?= =?ISO-8859-1?Q?b?=) (ab
Even multiple SPACEs between 'encoded-word's are
for the purpose of display
(=?ISO-8859-1?Q?a?= (ab
=?ISO-8859-1?Q?b?=)
Any amount of linear-space-white between 'encoded-word's
even if it includes a CRLF followed by one or more SPACEs
is ignored for the purposes of display
Moore Standards Track [Page 12]
RFC 2047 Message Header Extensions November 1996
(=?ISO-8859-1?Q?a_b?=) (a b
In order to cause a SPACE to be displayed within a
of encoded text, the SPACE MUST be encoded as part of
'encoded-word'.
(=?ISO-8859-1?Q?a?= =?ISO-8859-2?Q?_b?=) (a b
In order to cause a SPACE to be displayed between two
of encoded text, the SPACE MAY be encoded as part of one
the 'encoded-word's
9.
[RFC 822] Crocker, D., "Standard for the Format of ARPA Internet
Messages", STD 11, RFC 822, UDEL, August 1982.
[RFC 2049] Borenstein, N., and N. Freed, "Multipurpose Internet
Extensions (MIME) Part Five: Conformance Criteria and Examples",
RFC 2049, November 1996.
[RFC 2045] Borenstein, N., and N. Freed, "Multipurpose Internet
Extensions (MIME) Part One: Format of Internet Message Bodies",
RFC 2045, November 1996.
[RFC 2046] Borenstein N., and N. Freed, "Multipurpose Internet
Extensions (MIME) Part Two: Media Types", RFC 2046,
November 1996.
[RFC 2048] Freed, N., Klensin, J., and J. Postel, "
Internet Mail Extensions (MIME) Part Four:
Procedures", RFC 2048, November 1996.
Moore Standards Track [Page 13]
RFC 2047 Message Header Extensions November 1996
10. Security
Security issues are not discussed in this memo
11.
The author wishes to thank Nathaniel Borenstein, Issac Chan,
Donnerhacke, Paul Eggert, Ned Freed, Andreas M. Kirchwitz,
Jarnefors, Mike Rosin, Yutaka Sato, Bart Schaefer, and
Yamamoto, for their helpful advice, insightful comments,
illuminating questions in response to earlier versions of
specification
12. Author's
Keith
University of
107 Ayres
Knoxville TN 37996-1301
EMail: moore@cs.utk.
Moore Standards Track [Page 14]
RFC 2047 Message Header Extensions November 1996
Appendix - changes since RFC 1522 (in no particular order
+ explicitly state that the MIME-Version is not requried to
'encoded-word's
+ add explicit note that SPACEs and TABs are not allowed
'encoded-word's, explaining that an 'encoded-word' must look like
'atom' to an RFC822 parser.values, to be precise).
+ add examples from Olle Jarnefors (thanks!) which illustrate
encoded-words with adjacent linear-white-space are displayed
+ explicitly list terms defined in RFC822 and referenced in this
+ fix transcription typos that caused one or two lines and a couple
characters to disappear in the resulting text, due to nroff quirks
+ clarify that encoded-words are allowed in '*text' fields in
RFC822 headers and MIME body part headers, but NOT as
values
+ clarify the requirement to switch back to ASCII within the
portion of an 'encoded-word', for any charset that uses code
sequences
+ add a note about 'encoded-word's being delimited by "(" and ")"
within a comment, but not in a *text (how bizarre!).
+ fix the Andre Pirard example to get rid of the trailing "_"
the =E9. (no longer needed post-1342).
+ clarification: an 'encoded-word' may appear immediately
the initial "(" or immediately before the final ")" that delimits
comment, not just adjacent to "(" and ")" *within* *ctext
+ add a note to explain that a "B" 'encoded-word' will always have
multiple of 4 characters in the 'encoded-text' portion
+ add note about the "=" in the
+ note that processing of 'encoded-word's occurs *after* parsing,
some of the implications thereof
+ explicitly state that you can't expect to translate
1522 and either vanilla 822 or so-called "8-bit headers".
+ explicitly state that 'encoded-word's are not valid within
'quoted-string'.
Moore Standards Track [Page 15]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
