From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/18903 Path: main.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.gnus.general Subject: Re: MML: The Summation Date: 19 Nov 1998 03:54:01 +0100 Sender: owner-ding@hpc.uh.edu Message-ID: References: <199811181636.LAA29203@alderaan.gsfc.nasa.gov> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Trace: main.gmane.org 1035157348 8721 80.91.224.250 (20 Oct 2002 23:42:28 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 23:42:28 +0000 (UTC) Return-Path: Original-Received: from karazm.math.uh.edu (karazm.math.uh.edu [129.7.128.1]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id WAA29224 for ; Wed, 18 Nov 1998 22:27:16 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by karazm.math.uh.edu (8.9.1/8.9.1) with ESMTP id VAB04741; Wed, 18 Nov 1998 21:27:02 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 18 Nov 1998 21:26:50 -0600 (CST) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id VAA17089 for ; Wed, 18 Nov 1998 21:26:19 -0600 (CST) Original-Received: from sparky.gnus.org (ppp100.uio.no [129.240.240.105]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id WAA29150 for ; Wed, 18 Nov 1998 22:26:04 -0500 (EST) Original-Received: (from larsi@localhost) by sparky.gnus.org (8.8.5/8.8.5) id EAA06067; Thu, 19 Nov 1998 04:32:07 +0100 Mail-Copies-To: never X-Now-Reading: Elizabeth Hand's _Waking the Moon_ X-Now-Playing: Caterwaul's _Portent Hue_ Original-To: ding@gnus.org In-Reply-To: Vladimir Volovich's message of "18 Nov 1998 21:30:30 +0300" User-Agent: Gnus/5.070051 (Pterodactyl Gnus v0.51) XEmacs/21.2(beta3) (Aglaia) X-Face: &w!^oO~dS|}-P0~ge{$c!h\ writes: > Well, i'm also not sure whether MIME officially registered some of > Unicode encodings as allowable charsets for MIME parts, but if it is > so, then yes, there is a single charset which includes all those > languages, and much more. :-) But we have to consider that messages should be possible to read, shouldn't we? :-) I think a typical situation where you get a message with several charsets is when you quote messages written by people who use other charsets. I don't know heads nor tails of Japanese, but if I respond to a message from Katsumi Yamaoka / $B;32,(B $B9nH~(B (who posted using iso-2022-jp, and is likely not to be able to read Unicode replies), I'd like to respond using iso-2022-jp. And that I can do. --=-=-= Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit However, if I then naïvely uses a iso-8859-1 character in my response, I either have to find some superencoding that can encode all of this, or I have to post multipart. Since I can't read Unicode, I don't really see I have any real option here. -- (domestic pets only, the antidote for overdose, milk.) larsi@gnus.org * Lars Magne Ingebrigtsen --=-=-=--