From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Bruno Haible Newsgroups: gmane.emacs.devel Subject: Re: case-insensitive string comparison Date: Tue, 26 Jul 2022 20:56:10 +0200 Message-ID: <21545625.EfDdHjke4D@nimes> References: <837d3zdfco.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17697"; mail-complaints-to="usenet@ciao.gmane.io" Cc: sds@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jul 26 21:00:59 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oGPnf-0004RL-1D for ged-emacs-devel@m.gmane-mx.org; Tue, 26 Jul 2022 21:00:59 +0200 Original-Received: from localhost ([::1]:43316 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oGPnd-0003hF-P6 for ged-emacs-devel@m.gmane-mx.org; Tue, 26 Jul 2022 15:00:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44192) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oGPj7-0002PV-PT for emacs-devel@gnu.org; Tue, 26 Jul 2022 14:56:18 -0400 Original-Received: from mo4-p01-ob.smtp.rzone.de ([85.215.255.51]:40413) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oGPj4-00075e-AC; Tue, 26 Jul 2022 14:56:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1658861770; s=strato-dkim-0002; d=clisp.org; h=References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Cc:Date: From:Subject:Sender; bh=dIVaarCHxDS+jBnMypKOamaDXn3QxF1ifdP/jXo6W04=; b=e6kMhzz0rB6YI727k0aWaX5NSkig4jD9zBZOtTf60AbEp50SHdj+EoskZfrCt4XKud DEzPehFzVXvAqTBZbruwOXq8oycwHZtS2fMCY3YWCu1pUvviRMDpjOE9SBXphDcYGEMp lqzy/iQUVyUh+Qi4m+zP7tOgpg45ocpNMiDY+UHANN4SrBoMixD+ytrFIJJLixmQKUZO YVBmyueOWerPkTQ2C/Ah2Cf/bc83md/Hr1aiUidvaTlVbQg+lJ06jpagXvzZYfhLagdH ZQc7S3RiwE4Zd/cob7cNHiAgMwTuAYQY7+57mf3F7HJBfbmj0HqxwllUWTApU1eOMNFt jvAw== Authentication-Results: strato.com; dkim=none X-RZG-AUTH: ":Ln4Re0+Ic/6oZXR1YgKryK8brlshOcZlIWs+iCP5vnk6shH0WWb0LN8XZoH94zG6tLj91pDDiePUlLK7/NEvyfJON1C73DdIgA==" X-RZG-CLASS-ID: mo00 Original-Received: from nimes.localnet by smtp.strato.de (RZmta 47.47.0 AUTH) with ESMTPSA id g97246y6QIuA62H (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Tue, 26 Jul 2022 20:56:10 +0200 (CEST) In-Reply-To: <837d3zdfco.fsf@gnu.org> Received-SPF: none client-ip=85.215.255.51; envelope-from=bruno@clisp.org; helo=mo4-p01-ob.smtp.rzone.de X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:292713 Archived-At: Eli Zaretskii wrote: > With the > current machinery, a Lisp program or a user can control up/down-casing > by specifying a buffer-local case-table, and we won't give up this > important functionality. =46or which types of users, and for which use-cases, do you consider this an "important functionality"? Recall that the Unicode casing tables already cover the special cases for '=DF', Turkisch i, and so on. I'd like to understand whether per-user customization of casing rules is so important that libunistring should offer it in the API (as opposed to requiring code modifications). LibreOffice, for example, allows per-user customizations of the spell- checking dictionary, but not of the casing tables. Is that a flaw, and why? Bruno