From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Questions about isearch Date: Thu, 26 Nov 2015 09:46:09 -0500 Message-ID: References: <83lh9lx6oi.fsf@gnu.org> <87egfdant7.fsf@gmx.us> Reply-To: rms@gnu.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1448549210 18464 80.91.229.3 (26 Nov 2015 14:46:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 26 Nov 2015 14:46:50 +0000 (UTC) Cc: emacs-devel@gnu.org To: Steinar Bang Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 26 15:46:39 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 1a1xol-0003S9-64 for ged-emacs-devel@m.gmane.org; Thu, 26 Nov 2015 15:46:39 +0100 Original-Received: from localhost ([::1]:51609 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1xon-0008Rn-In for ged-emacs-devel@m.gmane.org; Thu, 26 Nov 2015 09:46:41 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49379) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1xoU-0008Le-Sl for emacs-devel@gnu.org; Thu, 26 Nov 2015 09:46:26 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a1xoT-0001HQ-SU for emacs-devel@gnu.org; Thu, 26 Nov 2015 09:46:22 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:40093) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1xoI-0001CD-BC; Thu, 26 Nov 2015 09:46:10 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1a1xoH-0004xa-TP; Thu, 26 Nov 2015 09:46:09 -0500 In-reply-to: (message from Steinar Bang on Wed, 25 Nov 2015 21:02:38 +0100) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e 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:195285 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > In Danish I would not consider this a ligature, but a separate letter. It > > can be written as ae, however. > Hm... could this happen other than when transcribing a Danish name > containing "æ" to an alphabet without Danish letters...? > > Thus, it would probably be nice to match it via ’ae’. > Speaking for the Norwegians: probably not! > > But where to stop? How about ’å’ (matched by ’a’)? > Absolutely not! > > Should it be captured by "aa"? > Actually perhaps yes, but only for names, and only if the locale is > Norwegian (and presumably also Danish). > Actually, considering the limitations, probably not. It seems that perhaps we need these correspondences to depend on the language in use. That's true for case conversion as well. For instance the way to upcase 'i' is 'I' in most languages, but in Turkish it's a character I can't find a way to enter in Emacs. It seems to me that we want to introduce a concept of current language which would control these things, and also the language for spell checking, and maybe some other things. In some cases, the current language is determined by which characters appear. That would work fine for scripts that are used for just one language. It would be hard to do that for Latin scripts, though. For latin scripts one might always have to specify it explicitly, but it could be specified by a file local variable or other such per-file customization mechanism. The language environment, which already exists, is something different. It controls how to recognize character codings, and therefore has to be global. The current language should be per-buffer and perhaps should vary between parts of a buffer. So they can't be the same thing. -- Dr Richard Stallman President, Free Software Foundation (gnu.org, fsf.org) Internet Hall-of-Famer (internethalloffame.org) Skype: No way! See stallman.org/skype.html.