From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Dave Love Newsgroups: gmane.emacs.devel Subject: Re: please consider emacs-unicode for pervasive changes Date: 05 Sep 2002 23:41:24 +0100 Sender: emacs-devel-admin@gnu.org Message-ID: References: <200208090754.g797s6s11972@rum.cs.yale.edu> <200208130030.JAA26246@etlken.m17n.org> <200209030615.PAA10378@etlken.m17n.org> <200209050548.OAA13998@etlken.m17n.org> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1031265711 7264 127.0.0.1 (5 Sep 2002 22:41:51 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 5 Sep 2002 22:41:51 +0000 (UTC) Cc: rms@gnu.org, raeburn@raeburn.org, monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 17n5Jt-0001su-00 for ; Fri, 06 Sep 2002 00:41:49 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17n5tl-0004hp-00 for ; Fri, 06 Sep 2002 01:18:53 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 17n5LT-0003tK-00; Thu, 05 Sep 2002 18:43:27 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 17n5Ji-0003q8-00 for emacs-devel@gnu.org; Thu, 05 Sep 2002 18:41:38 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 17n5Jg-0003pY-00 for emacs-devel@gnu.org; Thu, 05 Sep 2002 18:41:38 -0400 Original-Received: from albion.dl.ac.uk ([148.79.80.39]) by monty-python.gnu.org with esmtp (Exim 4.10) id 17n5Jd-0003oK-00; Thu, 05 Sep 2002 18:41:34 -0400 Original-Received: from fx by albion.dl.ac.uk with local (Exim 3.35 #1 (Debian)) id 17n5JU-0004gz-00; Thu, 05 Sep 2002 23:41:24 +0100 Original-To: Kenichi Handa Original-Lines: 26 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:7583 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:7583 Kenichi Handa writes: > Other application usually don't use such coding systems but > use iso-2022-jp, iso-2022-kr, etc. As charsets supported by > each of them doesn't overlap (thus not unified), reading and > writing by Emacs-unicode has no problem. But there will be a problem if you rely on coding system auto-detection. For instance, if you write out a buffer showing the jisx0208 charset as iso-2022-jp, Emacs 21 will auto-detect that encoding when you visit the file. However, Emacs 22 auto-detects it as iso-2022-7bit -- I don't know if this is a bug -- and if you then write it out, you'll get at least latin-iso8859-1 and chinese-gb2312 in the mix. I was particularly warning about iso-2022-7bit, i.e. many of the Emacs 21 files in lisp/{language,international}, and ChangeLogs (which rms already complained about) since this is going to developers. [For the benefit of others: Emacs 22 doesn't necessarily unify characters from CJK sets, in particular -- it's done explicitly in the Mule configuration, and can now be undone. However, as things stand, for example, you get a mixture of single- and double-width characters used for non-Japanese parts of japanese-jisx0208, and Chinese used for some of the Japanese, since a unification table for it is installed. Hence my remarks concerning lack of complete unification qua bug.]