From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Mon, 31 Jan 2005 13:40:48 -0500 From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] conversion of charsets in upas/fs In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable References: Topicbox-Message-UUID: 3a39d94a-eace-11e9-9e20-41e7f4b1d025 > | Content-Type: text/plain; charset=3DISO-8859-15; format=3Dflowed > | Content-Transfer-Encoding: 8bit >=20 > in the header doesn't lead to properly displayed 'umlauts', but >=20 > | Content-Type: text/plain; charset=3DISO-8859-15; format=3Dflowed > | Content-Transfer-Encoding: quoted-printable >=20 > does lead to properly displayed 'umlauts'. I don't believe Plan 9 is causing the problem. I just=20 manually sent myself an 8-bit 8859-15 message on Plan 9 with the script below and it came through just fine, at least using "mail" to read (didn't try acme Mail but they should be the same). Probably some mail server before Plan 9 is screwing with the 8-bit characters. Russ #!/usr/local/plan9/bin/rc { =09echo 'HELO rsc' =09sleep 2 =09echo 'MAIL FROM: ' =09sleep 2 =09echo 'RCPT TO: ' =09sleep 2 =09echo 'DATA' =09sleep 2 =09echo 'Content-Type: text/plain; charset=3DISO-8859-15; format=3Dflowed' =09echo 'Content-Transfer-Encoding: 8bit' =09echo =09echo Hello world. =09echo Here is an umlaut: =FC | tcs -t 8859-15 =09echo =09echo . =09sleep 2 =09echo QUIT =09sleep 2 } | dial -e tcp!204.178.31.2!25