From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel,gmane.emacs.bidi Subject: Re: merge emacs-bidi into the main tree Date: Fri, 15 Aug 2003 14:51:03 +0900 (JST) Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <200308150551.OAA28255@etlken.m17n.org> References: <20030811163200.38193.qmail@web14916.mail.yahoo.com> <200308130033.JAA25184@etlken.m17n.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1060926946 3109 80.91.224.253 (15 Aug 2003 05:55:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 15 Aug 2003 05:55:46 +0000 (UTC) Cc: emacs-bidi@gnu.org, emacs-devel@gnu.org, developer@arabeyes.org, shaikli@yahoo.com Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri Aug 15 07:55:44 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19nXYu-0008K7-00 for ; Fri, 15 Aug 2003 07:55:44 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19nXZm-0007qW-00 for ; Fri, 15 Aug 2003 07:56:38 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19nXVg-0006EW-I9 for emacs-devel@quimby.gnus.org; Fri, 15 Aug 2003 01:52:24 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19nXVV-0006EE-S9 for emacs-devel@gnu.org; Fri, 15 Aug 2003 01:52:13 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19nXUz-0005y1-Nj for emacs-devel@gnu.org; Fri, 15 Aug 2003 01:52:12 -0400 Original-Received: from [192.47.44.130] (helo=tsukuba.m17n.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19nXUR-0005e6-53; Fri, 15 Aug 2003 01:51:07 -0400 Original-Received: from fs.m17n.org (fs.m17n.org [192.47.44.2]) by tsukuba.m17n.org (8.11.6p2/3.7W-20010518204228) with ESMTP id h7F5p4u06635; Fri, 15 Aug 2003 14:51:04 +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.6/3.7W-20010823150639) with ESMTP id h7F5p3907076; Fri, 15 Aug 2003 14:51:04 +0900 (JST) Original-Received: (from handa@localhost) by etlken.m17n.org (8.8.8+Sun/3.7W-2001040620) id OAA28255; Fri, 15 Aug 2003 14:51:03 +0900 (JST) Original-To: rms@gnu.org In-reply-to: (message from Richard Stallman on Wed, 13 Aug 2003 23:08:07 -0400) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.2.92 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:15966 gmane.emacs.bidi:153 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:15966 In article , Richard Stallman writes: > So it sounds like some people are saying that the emacs-bidi code > is usable as it stands and is worth installing, and nobody thinks > it is useless. Meanwhile, it looks like you are ready to make > use of Eli's code in the short term. > If we can use Eli's code soon enough, then it's not worth installing > the Emacs-bidi code; it would just be extra work. On the other hand, > if it looks like the difficulty of using Eli's code is enough to make > it hard, then I think we should install the Emacs-bidi code now. Synchronizing emacs-unicode to HEAD will take a few weeks more. After that, I'll take a look at Eli's code and decide what to do. In any cases, I will install the changes for BIDI in the branch emacs-unicode-2 because the current codes of emacs-bidi depends on automatic-composition facitliy to display Arabic and Hebrew, and that exists only in emacs-unicode (and in emacs-bidi) version. I'd like to avoid the extra work of installing automatic-composition for the current HEAD. FYI, the automatic-composition is to call various character composition functions from the dipslay routine dynamically so that we don't have to run XXX-compose-region on file reading and character inputting. --- Ken'ichi HANDA handa@m17n.org