In article <[EMAIL PROTECTED]>,
Jean-Marc Desperrier <[EMAIL PROTECTED]> wrote:
> John Gardiner Myers wrote:
>
-snip-
> > Having Mozilla *generate* raw UTF-8 in headers is an entirely different
> > question.
>
> That's what it does now, but it's a bug.
>
> There is a feature, required by many users, that is to send raw data in
> local encoding.
>
>
> This is completely incompatible with the sending of raw UTF-8 in headers as
> there no systematic way to tell the difference between the two.
The current situation is completely undefined -- 8bit characters work
on an adhoc basis, no matter how they are sent (2047 or raw).
> Unfortunately, many users want that in the current state of things,
> and allowing to choose between the two behaviours, would be a lot
> more work in Mozilla than just doing the correction.
Having a pref for it would be the right thing to do, absent that,
sending UTF is not the /wrong/ thing to do, although it might not be as
initially pleasing to most people.
--
J.B. Moreno
