From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel,gmane.emacs.bidi Subject: Re: Now: Paragraph Direction Detection and Harmonization Date: Tue, 26 Apr 2011 22:23:03 +0300 Message-ID: <83fwp495rc.fsf@gnu.org> References: <83bpkgl113.fsf@gnu.org> <8362qbsj7p.fsf@gnu.org> <83y636grgj.fsf@gnu.org> <838vuy9prx.fsf@gnu.org> <834o5m9mxs.fsf@gnu.org> <83vcy27zzf.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: dough.gmane.org 1303845802 19942 80.91.229.12 (26 Apr 2011 19:23:22 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 26 Apr 2011 19:23:22 +0000 (UTC) Cc: emacs-bidi@gnu.org, emacs-devel@gnu.org To: Mohsen BANAN Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 26 21:23:18 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QEnqu-0003WO-GB for ged-emacs-devel@m.gmane.org; Tue, 26 Apr 2011 21:23:16 +0200 Original-Received: from localhost ([::1]:47681 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QEnqt-00011K-W0 for ged-emacs-devel@m.gmane.org; Tue, 26 Apr 2011 15:23:15 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:58158) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QEnqo-00010x-1y for emacs-devel@gnu.org; Tue, 26 Apr 2011 15:23:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QEnqn-00020T-6U for emacs-devel@gnu.org; Tue, 26 Apr 2011 15:23:10 -0400 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:41377) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QEnqk-00020C-Gb; Tue, 26 Apr 2011 15:23:06 -0400 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LK900B00XSBIO00@a-mtaout20.012.net.il>; Tue, 26 Apr 2011 22:22:59 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([84.228.59.73]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LK9008T8XU9HHQ0@a-mtaout20.012.net.il>; Tue, 26 Apr 2011 22:22:59 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-Received-From: 80.179.55.166 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:138810 gmane.emacs.bidi:884 Archived-At: > From: Mohsen BANAN > Cc: Mohsen BANAN , emacs-bidi@gnu.org, emacs-devel@gnu.org > Date: Tue, 26 Apr 2011 11:24:04 -0700 > > I don't know if there is a PICS-Proforma for > http://unicode.org/reports/tr9/. > > If there was, it would take the form of tables > refering to the base spec asking for details of > implementation with regard to each > section/option/feature/... of the specification. > > An example of PICS-Proforma in the RFC Series is: > http://tools.ietf.org/html/rfc1708 I don't think such a thing exists for UAX#9. There's Section 4 "Bidirectional Conformance"; Emacs implements everything it requires under "Full bidirectionality" class, as stated in the fragment of NEWS I cited. That's all there is to it. > In the absence of a PICS-Proforma, based on your > implementation details, you (or somebody) can go > through the specification and include emacs-bidi > implementation details and cross-referencing UAX#9 > sections. The source code in bidi.c already includes such cross-references. > Given the lack of precision for uniformity in > determination of say paragraph direction, based on > the emacs PICS, we can then visit our sisters at > Mozilla and have a conversation towards more > harmony. The algorithm used by Emacs to determine the paragraph base direction is exactly as prescribed by UAX#9. What differs, under the "high-level protocol" fire escape, is the definition of the paragraph. This definition is explained in the message I quoted earlier in this thread and in the Emacs User Manual. It is quite simple and easy to understand, so I really see no place for any misunderstanding.