From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: Problem of auto-fill-mode for wide character Date: Wed, 28 Dec 2005 16:46:27 +0900 Message-ID: References: NNTP-Posting-Host: main.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 1135757279 28737 80.91.229.2 (28 Dec 2005 08:07:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 28 Dec 2005 08:07:59 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 28 09:07:57 2005 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1ErWLj-0006mN-RF for ged-emacs-devel@m.gmane.org; Wed, 28 Dec 2005 09:07:56 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ErWN1-0000e8-P7 for ged-emacs-devel@m.gmane.org; Wed, 28 Dec 2005 03:09:16 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ErW2j-000420-Km for emacs-devel@gnu.org; Wed, 28 Dec 2005 02:48:18 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ErW2U-0003xU-1H for emacs-devel@gnu.org; Wed, 28 Dec 2005 02:48:16 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ErW2S-0003xI-Sb for emacs-devel@gnu.org; Wed, 28 Dec 2005 02:48:01 -0500 Original-Received: from [192.47.44.130] (helo=tsukuba.m17n.org) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1ErW2Y-0004xl-Uq for emacs-devel@gnu.org; Wed, 28 Dec 2005 02:48:08 -0500 Original-Received: from nfs.m17n.org (nfs.m17n.org [192.47.44.7]) by tsukuba.m17n.org (8.13.4/8.13.4/Debian-3) with ESMTP id jBS7kS3T030011; Wed, 28 Dec 2005 16:46:28 +0900 Original-Received: from etlken (etlken.m17n.org [192.47.44.125]) by nfs.m17n.org (8.13.4/8.13.4/Debian-3) with ESMTP id jBS7kSZj029129; Wed, 28 Dec 2005 16:46:28 +0900 Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1ErW0x-0005jN-00; Wed, 28 Dec 2005 16:46:27 +0900 Original-To: "Herbert Euler" In-reply-to: (herberteuler@hotmail.com) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) 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:48426 Archived-At: In article , "Herbert Euler" writes: > Hello everyone, > I'm very happy to see that Emacs supports Unicode internally, > but there is a problem in auto-fill-mode with this modification. > I'm going to explain why I think it's because of Unicode support. [...] > In the current Unicode 2 branch, Chinese characters are inserted > with the command 'self-insert-command' as ASCII characters. > This makes auto-fill in Chinese like other languages such as English, > since "in Auto Fill mode, lines are broken automatically _at spaces_ > when they get longer than the desired width". This is good to > languages in which words are separated with spaces, but at > least it's not appropriate for Chinese, because there are _no_ > spaces between Chinese characters. So one can force Emacs > auto-fill either by inserting spaces or by pressing M-q to invoke > 'fill-paragraph', both of them is not "natural" in Chinese editing. > Is my understanding correct? Could somebody help solve this > problem? Thanks. Thank you for reminding of this unsolved problem. The reason why Chinese characters invoke auto-fill is that they are not yet registered in the char-table auto-fill-chars. And why I have not yet done in Unicode 2 branch is that I don't know any "authorized" information about that. I've just registered these apparent characters: U+3041..U+30FF, U+3400..U+4DB5, U+4e00..U+9fbb, U+F900..U+FAFF, U+FF00..U+FF9F, U+20000..U+2FFFF So, now auto-fill should work for most Han characters. But, there are many more questionable characters, for instance: U+3000..U+303F, U+3200..U+33FF, ... Do you have some idea about exactly which set of characters to register in auto-fill-chars? --- Kenichi Handa handa@m17n.org