From mboxrd@z Thu Jan 1 00:00:00 1970 From: okamoto@granite.cias.osakafu-u.ac.jp Message-Id: <200008080347.XAA11396@cse.psu.edu> To: 9fans@cse.psu.edu Subject: Re: [9fans] ACME mail Date: Tue, 8 Aug 2000 12:48:37 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Topicbox-Message-UUID: f7c83bce-eac8-11e9-9e20-41e7f4b1d025 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, Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP. 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