Marshall Eubanks wrote:
You may have sent it in UTF-8, but arrived here as ASCII :
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by
mtagate3.uk.ibm.com id
jB5E0WQg115170
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: quoted-printable
Was that the intent ?
It wasn't *my* intent :-)
But in fact, that's the transfer encoding that got converted.
My outgoing transfer encoding was Content-Transfer-Encoding: 8bit
The content type was still tagged as UTF-8.
OTOH your response is tagged Content-Type: text/plain; charset=ISO-8859-1
and indeed did get converted somewhere, at your end I suspect.
It's not so easy to assert that UTF-8 just works.
Brian
Regards
Marshall
On Dec 5, 2005, at 9:00 AM, Brian E Carpenter wrote:
Hallam-Baker, Phillip wrote:
The fact that Brian is English and lives in Zurich is irrelevant.
As a matter of fact I don't live in Zürich; I live near Genève.
Of course this matters. The problem is that it's not quite as
straightforward as people think. I'm attempting to send this
in UTF-8; I wonder how many people will receive it correctly?
Brian
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf