Is it really the solution ? Please let me know...
In 5, after the paragraph :
This should be interpreted to mean that the message body (or
body part) is a base64 ASCII encoding of data that was
originally in ISO-8859-1, and will be in that character set
again after decoding.
Add a new paragraph like this one, but in good english :
It should be noted that, when textual data is to be encoded,
it must be submitted to the encoder with lines separated by
a CRLF sequence, and not with any other separator that
happens to be in local use. When textual data is decoded,
the inverse operation must be performed after the decoding.
Comment : clarification.
----------
In 5.1, change the beginning of Rule #1 to read :
Rule #1: (General 8-bit representation) Any octet,
except those that are part of a CRLF sequence, may be
represented by an "=" followed by a two digit
hexadecimal representation of the octet's value.
... etc etc
Comment : rule #1 was wrong : it did make reference to the local newline
convention, while text should be in 'Internet standard' form before the
encoding.
----------
In 5.1, change Rule #4 to read :
Rule #4 (Line Breaks): Any CRLF sequence appearing in
the data must be represented by a line break in the
Quoted- Printable encoding. Isolated CRs and LFs, or LF
CR sequences are not affected by this rule and must
thus be represented using the "=0D", "=0A" and "=0A=0D"
notations respectively. Since textual data to be
encoded must be presented to the encoder with lines
separated by CRLF sequences, this rule makes the
encoder to preserve the line breaks in textual data for
ease of human reading.
Comment : rule #4 was also wrong, since it did also make reference to the
local newline convention. More clarification added.
----------
In 7.1, just before the 7.1.1 title, add a paragraph like :
All forms of text must be transferred with lines separated
by CRLF sequences, as prescribed in RFC822. In particular,
when textual data must be content-transfer-encoded for
transport, local line separators must be replaced by CRLF
sequences before encoding. The reverse transformation must
be performed after decoding textual data.
Comment : clarification, clarification...
/AF