From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=) Newsgroups: gmane.mail.mew.general,gmane.emacs.devel Subject: [mew-int 01587] Re: windows 1252 Date: Tue, 04 Nov 2003 15:13:50 +0900 (JST) Message-ID: <20031104.151350.26530956.kazu@iijlab.net> References: <87llqzuvaj.fsf@tleepslib.sk.tsukuba.ac.jp> <20031104.111334.60445673.kazu@iijlab.net> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1067926461 19233 80.91.224.253 (4 Nov 2003 06:14:21 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 4 Nov 2003 06:14:21 +0000 (UTC) Original-X-From: mew-int-return-1587-gmmg-mew-int=m.gmane.org@mew.org Tue Nov 04 07:14:19 2003 Return-path: Original-Received: from mew2.iijlab.net ([202.232.15.102]) by deer.gmane.org with smtp (Exim 3.35 #1 (Debian)) id 1AGuSI-0005Fc-00 for ; Tue, 04 Nov 2003 07:14:18 +0100 Original-Received: (qmail 20495 invoked by uid 7800); 4 Nov 2003 06:14:12 -0000 Mailing-List: contact mew-int-help@mew.org; run by ezmlm Precedence: bulk List-Unsubscribe: Original-Received: (qmail 20483 invoked from network); 4 Nov 2003 06:14:11 -0000 Original-Received: from unknown (HELO omgo.iij.ad.jp) (202.232.30.157) by 202.232.15.102 with SMTP; 4 Nov 2003 06:14:11 -0000 Original-Received: from jc-smtp.iij.ad.jp ([192.168.176.35]) by omgo.iij.ad.jp (8.12.10/8.12.9) with ESMTP id hA46E7be020253; Tue, 4 Nov 2003 15:14:08 +0900 (JST) Original-Received: from localhost (jc-ssh.iij.ad.jp [192.168.174.22]) by jc-smtp.iij.ad.jp (8.12.10/8.12.9) with ESMTP id hA46Dd5Y022984; Tue, 4 Nov 2003 15:13:39 +0900 (JST) Original-To: emacs-devel@gnu.org, mew-int@mew.org In-Reply-To: X-Mailer: Mew version 4.0.61 on Emacs 21.3.50 / Mule 5.0 (SAKAKI) X-ML-Name: mew-int X-Mail-Count: 01587 Xref: main.gmane.org gmane.mail.mew.general:513 gmane.emacs.devel:17675 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:17675 From: Eli Zaretskii Subject: Re: [mew-int 01585] Re: windows 1252 > > The one-and-only coding-system which, I found, meets the requirements > > above is 'ctext. > > In that case, extending ctext to handle the problem we were discussing > in this thread would not be a good idea: IIRC, XEmacs doesn't support > extended segments, and non-MULE Emacsen certainly don't. Or am I > missing something? Speaking non-Mule Emacsen first, they can handle only US-ASCII and ISO-8859-1. They cannot display other character sets defined in ctext. But Mew users are happy because they use Mew in a proper way (see below). Some Mew users may ask a questoin: Q) I'm using Emacs 20.7 and when I received Japanese messages, Mew displays Japanese correctly. But when I use Mew on Emacs 19 and read a cache of Summary, the part written in Japanese is not displayed well. Why? The answer is: A) Since Emacs 19 does not support Japanese, Japanese cannot be displayed on Emacs 19. If you want to display Japanese, use Mew on Emacs 20.7. The situation is the same for XEmacs. Suppose we extend ctext of Emacs 21.4 to handle window 125x. Q) I'm using Emacs 21.4 and when I received window 125x, Mew displays it correctly. But when I use XEmacs, it displayed broken. Why? A) ctext of XEmacs cannot handle window 125x. If you want to display window 125x, use Mew on Emacs 21.4. Note that this method of Mew has been surviving for last ten years on the multi-language and multi-Emacs environment. --Kazu