From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Bug 130397 Date: Tue, 18 Jan 2005 12:44:52 +0200 Organization: JURTA Message-ID: <878y6rnhd3.fsf@jurta.org> References: <20040517120658.GA6919@agmartin.aq.upm.es> <20041217121515.GA2270@agmartin.aq.upm.es> <200412221237.VAA07262@etlken.m17n.org> <20041222171306.GA4462@agmartin.aq.upm.es> <200501041250.VAA10883@etlken.m17n.org> <200501050200.LAA12589@etlken.m17n.org> <873bxgjxrp.fsf-monnier+emacs@gnu.org> <200501050550.OAA13142@etlken.m17n.org> <20050107153618.GA1508@agmartin.aq.upm.es> <878y7553qd.fsf@jurta.org> <200501130559.OAA12786@etlken.m17n.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1106047980 28113 80.91.229.6 (18 Jan 2005 11:33:00 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 18 Jan 2005 11:33:00 +0000 (UTC) Cc: agustin.martin@hispalinux.es, emacs-devel@gnu.org, k.stevens@ieee.org, ispell-el-bugs@itcorp.com, 130397@bugs.debian.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 18 12:32:52 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CqrbQ-00042D-00 for ; Tue, 18 Jan 2005 12:32:52 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CqrmJ-0001MR-Aw for ged-emacs-devel@m.gmane.org; Tue, 18 Jan 2005 06:44:07 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Cqrla-0001Dk-SH for emacs-devel@gnu.org; Tue, 18 Jan 2005 06:43:23 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CqrlX-0001Bp-VQ for emacs-devel@gnu.org; Tue, 18 Jan 2005 06:43:20 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Cqrb0-0007pq-G6 for emacs-devel@gnu.org; Tue, 18 Jan 2005 06:32:26 -0500 Original-Received: from [194.126.101.100] (helo=MXR-1.estpak.ee) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Cqr6E-0004wy-JK for emacs-devel@gnu.org; Tue, 18 Jan 2005 06:00:38 -0500 Original-Received: from mail.neti.ee (80-235-38-192-dsl.mus.estpak.ee [80.235.38.192]) by MXR-1.estpak.ee (Postfix) with ESMTP id 640D414C388; Tue, 18 Jan 2005 13:00:27 +0200 (EET) Original-To: Kenichi Handa In-Reply-To: <200501130559.OAA12786@etlken.m17n.org> (Kenichi Handa's message of "Thu, 13 Jan 2005 14:59:21 +0900 (JST)") User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux) X-Virus-Scanned: by amavisd-new-2.2.1 (20041222) (Debian) at neti.ee 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: main.gmane.org gmane.emacs.devel:32327 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:32327 Kenichi Handa writes: > Please try the latest ispell.el. I think at least this > misalignment error is fixed now. I tried the latest ispell.el and I see that your change is a definite improvement since it now allows to check words in mule-unicode charsets. But it still doesn't fix the misalignment error. It even makes this error more frequent because it now occurs in all UTF-8 texts checked with ispell-region (which earlier were simply skipped before your change). The cause of the error is the following: a line sent by ispell.el to the ispell process is converted from mule-unicode charset to the process charset, and the accepted output gets converted from process coding to the internal Emacs charset iso8859. So `search-forward' in `ispell-process-line' fails to find a string in iso8859 charset in the buffer with the same string in mule-unicode charset. > As for this, I agree with the following statement. > > Geoff Kuenning writes: >> I'm not entirely sure what you mean here. For disjoint alphabets, >> it's certainly relatively easy to figure out which word should go to >> which ispell instance. For identical, superset, or overlapping >> alphabets, the problem is basically insoluable. For example, "fra" is >> a misspelling in English but legal in Italian. If it appears in a >> mixed passage, which dictionary should it be fed to? The only >> solution would seem to be to require the user to mark passages in some >> way, as is done in HTML. I agree that marking would help ispell.el to decide which dictionary to use on a word. However, even without marking users might still prefer to check words simultaneously with multiple dictionaries and to accept a word when it's found in one dictionary, because such cases where a word appears in both dictionaries might be too rare for two chosen languages. A similar problem exists even within one language where a misspelled word is still a valid word according to ispell (e.g. misspelled "male" instead of "mail"). -- Juri Linkov http://www.jurta.org/emacs/