On Mon, 18 Mar 2002, Randall Gellens <randy(_at_)qualcomm(_dot_)com> wrote:
If either character is not 7-bit US ASCII, then use language-specific
folding rules to decide if the SP should be deleted or not. Since the
point of f=f is to permit line wrapping, the client needs
language-specific rules anyway. It just needs to now apply them during
f=f decoding as well.
Presumably there will be an extra parameter in the Content-Type header
to specify language and hence what language-specific rules need to be
applied?
For example, this f=f message will have wrapped at a utf-8 encoded €
character. Deployed clients will be sending this sort of stuff so it is
important that any new arrangements take this into account.
Is the solution just to add a flow-language=parameter for f=f, with the
default action to do just what is done now?
If there is violent objection to the above, the alternate solution is a
new format parameter (content-type=text/plain; format=wrap) with the
rule that a SP CRLF is inserted as desired, and deleted on receipt. The
current f=f would be depricated.
The worry may be that such a big change will be seen as a good reason
for those clients which still abuse CT=text/plain, CTE=qp to continue
what they are doing.
--
Ian Bell T U R N P I K E