From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Agustin Martin Newsgroups: gmane.emacs.devel Subject: Re: Adding ispell-multi.el and friends to Emacs Date: Thu, 21 Jun 2007 01:09:30 +0200 Message-ID: <20070620230930.GA3279@agmartin.aq.upm.es> References: <87ejkchlh2.fsf@heslin.eclipse.co.uk> <20070617210511.GB5230@agmartin.aq.upm.es> <87645ml132.fsf@jurta.org> <87abuygoqo.fsf@heslin.eclipse.co.uk> <20070618095506.GA4724@agmartin.aq.upm.es> <46767C02.4080806@gmx.at> <20070619131400.GA10763@agmartin.aq.upm.es> <4679218B.60504@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1182382069 658 80.91.229.12 (20 Jun 2007 23:27:49 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 20 Jun 2007 23:27:49 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 21 01:27:47 2007 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 1I19aU-0000sW-PP for ged-emacs-devel@m.gmane.org; Thu, 21 Jun 2007 01:27:47 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I19aU-0003oJ-7l for ged-emacs-devel@m.gmane.org; Wed, 20 Jun 2007 19:27:46 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I19Zz-0003at-Hi for emacs-devel@gnu.org; Wed, 20 Jun 2007 19:27:15 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I19Zy-0003aV-L8 for emacs-devel@gnu.org; Wed, 20 Jun 2007 19:27:15 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I19Zy-0003aL-Ie for emacs-devel@gnu.org; Wed, 20 Jun 2007 19:27:14 -0400 Original-Received: from edison.ccupm.upm.es ([138.100.4.49]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1I19Zx-000565-U6 for emacs-devel@gnu.org; Wed, 20 Jun 2007 19:27:14 -0400 Original-Received: from debian ([138.100.247.74]) by edison.ccupm.upm.es (8.13.8/8.13.8) with ESMTP id l5KNR1Pu015112; Thu, 21 Jun 2007 01:27:01 +0200 Original-Received: by debian (Postfix, from userid 1000) id C389117E6F; Thu, 21 Jun 2007 01:09:30 +0200 (CEST) Content-Disposition: inline In-Reply-To: <4679218B.60504@gmx.at> User-Agent: Mutt/1.5.13 (2006-08-11) X-detected-kernel: Linux 2.4-2.6 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:73479 Archived-At: On Wed, Jun 20, 2007 at 02:46:03PM +0200, martin rudalics wrote: > >>FWIW, I have misalignment clashes only when Emacs and the spell system > >>disagree about the coding system. In that case, however, the output > >>of the spell system is unusable for single words too. > > > > > > Unless communication is done in utf8, if you have an utf8 buffer with a > char > > not in the dict charset ispell-region will fail with a misalingment (at > > least with ispell, most aspell communications are done in utf8), but if > you > > try ispell-word in that word, the foreign char will not be recognized as > > part of a word and only part of it will be sent to ispell for testing. The > > difference is that ispell-region will fail for all the region if a > > misalignment appear while ispell-word will only do things differently for > > the affected word. That was the intention. > > Personally, I don't care whether a word, line, region or buffer appears > corrupted. I'd discontinue spell-checking in any of these cases. Sometimes you know what happened and can continue. > The interface (ispell.el) has to check which coding system should get > applied. Agreed, and the interface should avoid sending words with non supported chars in case a word with them is present (as with a foreign word) or at least discriminate properly. What I mean is that is difficult to do that when a line is sent as a whole to the ispell process. When things are done word-by-word that is possible, but this is of small efficiency in large buffers. > The user has to check whether the interface got it right and, > if necessary, be able to override wrong settings. BTW, I don't use utf8 > to communicate with Aspell and did not encounter any problems so far. You probably use it implicitely unless you use an explicitely user defined non-utf8 dict entry. >>From ispell.el, (defun ispell-aspell-find-dictionary (dict-name) ... (list "-d" dict-name "--encoding=utf-8") ... 'utf-8)) BTW, I have just reproduced it with emacs21, aspell and the old ispell.el. I admit that this is currently (emacs 22) a problem only with ispell or with buggy user-defined entries. Anyway, this subthread started when Peter considered using the word-by-word mechanism and I pointed out that it might not be efficient in large buffers. I do not think this is now adding much to that. -- Agustin