From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: Re: Questions about isearch Date: Wed, 25 Nov 2015 20:14:06 +0000 Message-ID: References: <83lh9lx6oi.fsf@gnu.org> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1140118eaa0d32052563191f X-Trace: ger.gmane.org 1448482454 25633 80.91.229.3 (25 Nov 2015 20:14:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 25 Nov 2015 20:14:14 +0000 (UTC) Cc: emacs-devel To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 25 21:14:12 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 1a1gSB-0007eV-7W for ged-emacs-devel@m.gmane.org; Wed, 25 Nov 2015 21:14:11 +0100 Original-Received: from localhost ([::1]:47483 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1gSD-0007hB-1B for ged-emacs-devel@m.gmane.org; Wed, 25 Nov 2015 15:14:13 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43175) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1gS9-0007h4-V3 for emacs-devel@gnu.org; Wed, 25 Nov 2015 15:14:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a1gS8-0005Mg-Qa for emacs-devel@gnu.org; Wed, 25 Nov 2015 15:14:09 -0500 Original-Received: from mail-lf0-x22f.google.com ([2a00:1450:4010:c07::22f]:35465) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1gS7-0005M9-2L; Wed, 25 Nov 2015 15:14:07 -0500 Original-Received: by lfdl133 with SMTP id l133so73725722lfd.2; Wed, 25 Nov 2015 12:14:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ChKvaRFHZv1MAUB7Jm8iRUfW9HwVNjsxXC3xamlJNgc=; b=d9axzonPxH37P1x0AYAs0Hq63aNSMgZVHEYO+SOoEC1pOmgUiwVZavjvNIZw71OF+B p3ZtCeiASY5oKUNnx/VWrLA0+n7nCj7ehumZ/KrFG7wXGG/edOdMvYHMbznxBeh+fYVU RZOfkIHIY4IC5tGWe3FRzSwfJ4e/uB//36MINlezLRJrtY3BoF4Nn0SbIXkJs0gbcgW9 KCtLJHmJPYpVN0GFUVvVmoMRhaisEnXpurD6W3L1cPEdrHq56cP2uQxtL/O4GOfgdzN6 1al5S469tGQ8rB9W+x3zjENAHN3U9jXiOyAdpqTPCQoPOCV0cbMPTNGASvNrmDaWmtRx k5Ag== X-Received: by 10.25.208.206 with SMTP id h197mr16721962lfg.153.1448482446115; Wed, 25 Nov 2015 12:14:06 -0800 (PST) Original-Received: by 10.112.202.99 with HTTP; Wed, 25 Nov 2015 12:14:06 -0800 (PST) Original-Received: by 10.112.202.99 with HTTP; Wed, 25 Nov 2015 12:14:06 -0800 (PST) In-Reply-To: <83lh9lx6oi.fsf@gnu.org> X-Google-Sender-Auth: MT0RlJWpWpbYECMAn7iEYhQuk0w X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c07::22f 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:195250 Archived-At: --001a1140118eaa0d32052563191f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 25 Nov 2015 6:41 pm, "Eli Zaretskii" wrote: > 1. Character folding doesn't catch ligatures, such as =C3=A6 (should it m= atch > the two characters "ae")? I've no idea. It would be easy to add. Those who use ligatures need to tell us whether that makes sense. > 2. It also doesn't match =C3=A4 (a single character) with a=CC=88 (2 char= acters, > which Emacs correctly composes into 1 grapheme cluster). Should it? Possibly. Since they look the same, might make things easier on users. But I wouldn't know as I've never seen the second version used anywhere. > 4. What is the equivalent of case-replace and the letter-case related > behavior of replace commands to character folding? E.g., if the > replace command specifies to replace "foo" with "bar", and we found > "f=C3=B6o", should we replace it with "b=C3=A4r" or something, by analogy= with > letter-case behavior? I don't think we should do that. Case replacement makes sense because the way you capitalize a word is frequently (though not always) independent of the word itself. That's not the case with char folding. At least in Portuguese, accents only go in very specific places, and I would _never_ want emacs to add an accent to the replacement text just because the word being replaced happened to have an accent. --001a1140118eaa0d32052563191f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 25 Nov 2015 6:41 pm, "Eli Zaretskii" <eliz@gnu.org> wrote:
> 1. Character folding doesn't catch ligatures, such as =C3=A6 (shou= ld it match
> the two characters "ae")?

I've no idea. It would be easy to add.
Those who use ligatures need to tell us whether that makes sense.

> 2. It also doesn't match =C3=A4 (a single character= ) with a=CC=88 (2 characters,
> which Emacs correctly composes into 1 grapheme cluster).=C2=A0 Should = it?

Possibly. Since they look the same, might make things easier= on users. But I wouldn't know as I've never seen the second versio= n used anywhere.

> 4. What is the equivalent of case-replace and the lette= r-case related
> behavior of replace commands to character folding?=C2=A0 E.g., if the<= br> > replace command specifies to replace "foo" with "bar&qu= ot;, and we found
> "f=C3=B6o", should we replace it with "b=C3=A4r" o= r something, by analogy with
> letter-case behavior?

I don't think we should do that. Case replacement makes = sense because the way you capitalize a word is frequently (though not alway= s) independent of the word itself. That's not the case with char foldin= g. At least in Portuguese, accents only go in very specific places, and I w= ould _never_ want emacs to add an accent to the replacement text just becau= se the word being replaced happened to have an accent.

--001a1140118eaa0d32052563191f--