9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ACME mail
Date: Tue,  8 Aug 2000 12:48:37 +0900	[thread overview]
Message-ID: <200008080347.XAA11396@cse.psu.edu> (raw)

Thanks Bob.

>we keep ed around for use on our unix systems.  ned uses
>the upas/fs to serve a mailbox and marshall to compose a

I looked the source of marshall, and found that it supposes only
UTF-8 or US-ASCII for sending out charset.  In Japan, many
living in the other world than us use ISO-2022-JP charset
for exchanging email.

So, the interest is:

(1)We should send out ISO-2022-JP charset email, if we want to
keep good relation with them.  Of course, we can send Mime
formatted UTF-8, but in that case, we may lose something. 
(This is mailing-list is aliased to "UTF-8 mailing-list", so we
can use UTF-8 ?).

(2) I want to have UTF-8 charset files in our disk if it is plain/text, 
for the sake that we can read it anytime.  Then, I suppose it may 
be better to convert ISO-2022-JP formatted mail to UTF-8 when 
we received it.  In this case, then, we'll have a UTF-8 charset
file of, say,

<UTF-8 charset headers>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-2022-JP.

<body of UTF-8 charset content>

When I see the sources under /sys/src/cmd/upas, there
seems to be a different principle.  There, we'll have IS-2022-JP
charset file same to its orignal form. How do you think (all)?

Kenji



             reply	other threads:[~2000-08-08  3:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-08  3:48 okamoto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-05-25  7:11 [9fans] Acme Mail Skip Tavakkolian
2010-05-25 14:11 ` David Leimbach
2010-05-25 14:19 ` erik quanstrom
2010-05-25 15:34   ` Skip Tavakkolian
2010-05-25 15:42     ` Skip Tavakkolian
2010-05-25 15:55       ` ron minnich
2010-05-25 18:13         ` erik quanstrom
2010-05-25 20:53         ` Mathieu Lonjaret
2010-05-25 22:45           ` Skip Tavakkolian
2010-05-26  0:06             ` Akshat Kumar
2010-05-26  1:14               ` Russ Cox
2010-05-26  1:55                 ` Lyndon Nerenberg
2010-05-27  0:14                   ` erik quanstrom
2010-05-27  0:56                     ` Lyndon Nerenberg
2010-05-27  1:02                       ` erik quanstrom
2005-12-07 10:35 Lucio De Re
2000-08-08 23:59 [9fans] ACME mail okamoto
2000-08-08 22:50 ` Boyd Roberts
2000-08-08 23:49 okamoto
2000-08-08 14:47 Russ Cox
2000-08-08 11:24 presotto
2000-08-08 10:18 okamoto
2000-08-08  8:54 forsyth
2000-08-08  4:54 okamoto
2000-08-08  4:45 forsyth
2000-08-07 12:21 bobf
2000-08-07  3:33 okamoto
2000-08-02 15:49 lucio

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=200008080347.XAA11396@cse.psu.edu \
    --to=okamoto@granite.cias.osakafu-u.ac.jp \
    --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).