From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: please consider emacs-unicode for pervasive changes Date: Fri, 6 Sep 2002 13:46:36 +0900 (JST) Sender: emacs-devel-admin@gnu.org Message-ID: <200209060446.NAA15758@etlken.m17n.org> References: NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1031288060 18804 127.0.0.1 (6 Sep 2002 04:54:20 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 6 Sep 2002 04:54:20 +0000 (UTC) Cc: 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 17nB8M-0004tA-00 for ; Fri, 06 Sep 2002 06:54:18 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17nBiN-0005Ae-00 for ; Fri, 06 Sep 2002 07:31:31 +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 17nB9z-0004NJ-00; Fri, 06 Sep 2002 00:55:59 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 17nB8F-0004LD-00 for emacs-devel@gnu.org; Fri, 06 Sep 2002 00:54:11 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 17nB8C-0004KK-00 for emacs-devel@gnu.org; Fri, 06 Sep 2002 00:54:10 -0400 Original-Received: from tsukuba.m17n.org ([192.47.44.130]) by monty-python.gnu.org with esmtp (Exim 4.10) id 17nB8B-0004Jl-00 for emacs-devel@gnu.org; Fri, 06 Sep 2002 00:54:08 -0400 Original-Received: from fs.m17n.org (fs.m17n.org [192.47.44.2]) by tsukuba.m17n.org (8.11.6/3.7W-20010518204228) with ESMTP id g864kbK03395; Fri, 6 Sep 2002 13:46:37 +0900 (JST) (envelope-from handa@m17n.org) Original-Received: from etlken.m17n.org (etlken.m17n.org [192.47.44.125]) by fs.m17n.org (8.11.3/3.7W-20010823150639) with ESMTP id g864kad20154; Fri, 6 Sep 2002 13:46:36 +0900 (JST) Original-Received: (from handa@localhost) by etlken.m17n.org (8.8.8+Sun/3.7W-2001040620) id NAA15758; Fri, 6 Sep 2002 13:46:36 +0900 (JST) Original-To: eliz@is.elta.co.il In-Reply-To: (message from Eli Zaretskii on Thu, 5 Sep 2002 16:48:28 +0200 (IST)) 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:7610 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:7610 In article , Eli Zaretskii writes: > On Thu, 5 Sep 2002, Kenichi Handa wrote: >> As Emacs-unicode unifies, for instance, character C1 of >> charset CS1 and character C2 of CS2. So, so even if an >> original iso-2022-7bit file uses the different byte sequence >> to represent them, when emacs reads it and write, C2 will be >> encoded by the same byte sequence as C1. >> >> It doesn't matter for Emacs because when Emacs reads that >> file again, there's no difference. > As an example of a situation where it does matter, consider this: you > visit a file, edit some parts of it, then save it. It would be > reasonable to expect that portions of the file you didn't change will > compare equal to the original file. In other words, running `diff' on > the original and the edited files will not show any changes in those line > you didn't modify. But, `diff' is another program. Emacs' ediff-files should work well. And, please note that even Emacs 21 don't preserve the same byte sequence for iso-2022-7bit file in rare case. This problem can actually be ignored only because such a case is very very rare. Anyway, I'm not claiming that we don't have to solve this problem. Just I have more urgent tasks for the moment. --- Ken'ichi HANDA handa@etl.go.jp