From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: find-composition still depends on the composition property Date: Wed, 22 Oct 2008 21:35:40 +0200 Message-ID: References: <87tzbh7kd9.fsf@jurta.org> <87tzb5ikrw.fsf@jurta.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: ger.gmane.org 1224704283 4081 80.91.229.12 (22 Oct 2008 19:38:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 22 Oct 2008 19:38:03 +0000 (UTC) Cc: juri@jurta.org, emacs-devel@gnu.org To: Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 22 21:39:04 2008 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KsjXr-0000rN-14 for ged-emacs-devel@m.gmane.org; Wed, 22 Oct 2008 21:39:04 +0200 Original-Received: from localhost ([127.0.0.1]:38816 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KsjWj-0000Yr-9k for ged-emacs-devel@m.gmane.org; Wed, 22 Oct 2008 15:37:53 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KsjUX-0007PE-HD for emacs-devel@gnu.org; Wed, 22 Oct 2008 15:35:37 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KsjUW-0007OE-D9 for emacs-devel@gnu.org; Wed, 22 Oct 2008 15:35:37 -0400 Original-Received: from [199.232.76.173] (port=41272 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KsjUW-0007O9-9V for emacs-devel@gnu.org; Wed, 22 Oct 2008 15:35:36 -0400 Original-Received: from mtaout1.012.net.il ([84.95.2.1]:64824) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KsjUV-0005Zx-Kx for emacs-devel@gnu.org; Wed, 22 Oct 2008 15:35:36 -0400 Original-Received: from HOME-C4E4A596F7 ([77.126.98.197]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0K9500FQ9NTRNF90@i-mtaout1.012.net.il> for emacs-devel@gnu.org; Wed, 22 Oct 2008 21:37:04 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.gnu.org: Solaris 9.1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:104855 Archived-At: > From: Kenichi Handa > Date: Wed, 22 Oct 2008 14:29:47 +0900 > Cc: juri@jurta.org, emacs-devel@gnu.org >=20 > In article , Kenichi Handa writes: >=20 > > Ah, it's not a bug of composition, but a bug of scan_words > > (syntax.c). Currently U+301 is labeled as `latin' script, > > and the surrounding characters there are `cyrillic' script. > > Thus, that funciton thinks that there's a word boundary. > > I'll find a way to solve this problem. >=20 > I've just installed a fix. Thanks, but Emacs still does not get this quite right. For example, in the following line: =D7=90=D7=91=D7=92=D7=93=D7=9412345 Which mixes Hebrew letters with digits, M-f stops at the first digit, whereas in this line: abcde12345 it does not. The latter behavior is correct, the former is not. (I'= m ashamed to admit that even MS Word gets it right.) I understand that the way for fixing this would be to install more entries in word-combining-categories, but more infrastructure seems t= o be missing, since right now no characters have the "Hebrew" category, for example (at least judging by the output of describe-categories). By the way, I'd suggest to move the legend generated by describe-categories to the beginning of the buffer, because the buffe= r is huge and it does not say anywhere at the beginning that there's a legend at the end. Without the legend, the buffer looks like a large pile of gibberish. And another wish: can we have word-combining-categories and word-separating-categories display their elements with human-readable letters, not as their ASCII codes? (Quick: what letter is code 94?)