9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] conversion of charsets in upas/fs
Date: Mon, 31 Jan 2005 13:40:48 -0500	[thread overview]
Message-ID: <ee9e417a050131104058a86657@mail.gmail.com> (raw)
In-Reply-To: <f65ac96a9439a20d5d794458b0371e86@voidness.de>

> | Content-Type: text/plain; charset=ISO-8859-15; format=flowed
> | Content-Transfer-Encoding: 8bit
> 
> in the header doesn't lead to properly displayed 'umlauts', but
> 
> | Content-Type: text/plain; charset=ISO-8859-15; format=flowed
> | Content-Transfer-Encoding: quoted-printable
> 
> does lead to properly displayed 'umlauts'.

I don't believe Plan 9 is causing the problem.  I just 
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

{
	echo 'HELO rsc'
	sleep 2
	echo 'MAIL FROM: <rsc@swtch.com>'
	sleep 2
	echo 'RCPT TO: <glenda@plan9.bell-labs.com>'
	sleep 2
	echo 'DATA'
	sleep 2
	echo 'Content-Type: text/plain; charset=ISO-8859-15; format=flowed'
	echo 'Content-Transfer-Encoding: 8bit'
	echo
	echo Hello world.
	echo Here is an umlaut: ü | tcs -t 8859-15
	echo
	echo .
	sleep 2
	echo QUIT
	sleep 2
} | dial -e tcp!204.178.31.2!25


  reply	other threads:[~2005-01-31 18:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-29 13:57 Heiko Dudzus
2005-01-31  1:21 ` Kenji Okamoto
2005-01-31 14:05   ` Heiko Dudzus
2005-01-31 18:40     ` Russ Cox [this message]
2005-01-31 19:19       ` boyd, rounin
2005-02-01  8:24       ` Heiko Dudzus
2005-02-01 10:29         ` Heiko Dudzus
2005-02-01 17:11           ` Heiko Dudzus
2005-02-01 20:41             ` Sape Mullender
2005-02-01 20:45               ` boyd, rounin
2005-02-01 18:26           ` Russ Cox
2005-02-01 18:37             ` rog
2005-02-01 19:50               ` boyd, rounin
2005-02-02 10:59               ` Heiko Dudzus
2005-02-02 13:48                 ` Russ Cox
2005-02-02 23:41                   ` Heiko Dudzus
2005-02-01  1:42     ` Kenji Okamoto
2005-02-01  3:42       ` Russ Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ee9e417a050131104058a86657@mail.gmail.com \
    --to=russcox@gmail.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).