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: Questions about isearch Date: Fri, 27 Nov 2015 10:53:50 +0200 Message-ID: <83zixzsu01.fsf@gnu.org> References: <83lh9lx6oi.fsf@gnu.org> <87egfdant7.fsf@gmx.us> <83h9k8vig7.fsf@gnu.org> <83oaegtqxq.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1448614474 3257 80.91.229.3 (27 Nov 2015 08:54:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 27 Nov 2015 08:54:34 +0000 (UTC) Cc: per@starback.se, sb@dod.no, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 27 09:54:23 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1a2EnN-0006I2-CL for ged-emacs-devel@m.gmane.org; Fri, 27 Nov 2015 09:54:21 +0100 Original-Received: from localhost ([::1]:55393 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2EnP-0005Xv-QY for ged-emacs-devel@m.gmane.org; Fri, 27 Nov 2015 03:54:23 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41111) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2EnB-0005Xo-Uo for emacs-devel@gnu.org; Fri, 27 Nov 2015 03:54:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a2En8-0000Eu-Fx for emacs-devel@gnu.org; Fri, 27 Nov 2015 03:54:09 -0500 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:56593) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2En8-0000Dk-7d; Fri, 27 Nov 2015 03:54:06 -0500 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0NYG00E00TX4E700@a-mtaout20.012.net.il>; Fri, 27 Nov 2015 10:54:04 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([84.94.185.246]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NYG00E1WU24DU10@a-mtaout20.012.net.il>; Fri, 27 Nov 2015 10:54:04 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 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:195359 Archived-At: > From: Richard Stallman > CC: per@starback.se, emacs-devel@gnu.org, sb@dod.no > Date: Fri, 27 Nov 2015 01:38:32 -0500 > > You seem to be trying to design an ultimate, ideal current language > facility. Yes. > We might want to get there eventually, but I think we should start > with something simple. IMO, the initial implementation could have only partial support for multiple languages, but the design should allow for extending that all the way towards the eventual goal, which cannot possibly be a single language per buffer, not in Emacs 2X. > After all, most buffers have only one language in them. Not in my experience: buffers that combine English and Hebrew are something I see every day. The simplest example is email: the headers are in English, while the body is in a mix of Hebrew and Latin (usually English) words. > Having a selectable language for the whole buffer is going to be > better than the current situation where you can't select it. I agree. > If you have a table in Turkish in the middle of a English document, > and you want to sort the table, you can switch the buffer to Turkish, > sort, and switch back to English. Language-specific processing is not limited to sorting contiguous regions in the buffer. This discussion started from Isearch, so the example which underlines the issues is searching for a string with character-folding enabled -- this should automatically apply language-specific rules when it hits a possible match in the Turkish portion, then switch back to English when the match is in the English part. Same with spelling -- you'd want flyspell to use the right language in each portion, without the need to restart the speller program with another dictionary.