From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: CSV parsing and other issues (Re: LC_NUMERIC) Date: Mon, 07 Jun 2021 15:28:38 +0300 Message-ID: <83a6o1hn9l.fsf@gnu.org> References: <20210606233638.v7b7rwbufay5ltn7@E15-2016.optimum.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3793"; mail-complaints-to="usenet@ciao.gmane.io" Cc: manikulin@gmail.com, emacs-devel@gnu.org To: Boruch Baum Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jun 08 02:10:12 2021 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 1lqPJs-0000hF-8W for ged-emacs-devel@m.gmane-mx.org; Tue, 08 Jun 2021 02:10:12 +0200 Original-Received: from localhost ([::1]:47526 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lqPJr-00065Y-7W for ged-emacs-devel@m.gmane-mx.org; Mon, 07 Jun 2021 20:10:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55724) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lqPFE-00082h-AH for emacs-devel@gnu.org; Mon, 07 Jun 2021 20:05:24 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:39408) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lqPFD-0000H0-O8; Mon, 07 Jun 2021 20:05:23 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1473 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lqEN1-0005MA-Kh; Mon, 07 Jun 2021 08:28:44 -0400 In-Reply-To: <20210606233638.v7b7rwbufay5ltn7@E15-2016.optimum.net> (message from Boruch Baum on Sun, 6 Jun 2021 19:36:38 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:270542 Archived-At: > Date: Sun, 6 Jun 2021 19:36:38 -0400 > From: Boruch Baum > Cc: Maxim Nikulin , Eli Zaretskii > > 1] @Maxim: You seemed to indicate that the default emacs locale is 'C'. > That may be true That's only true for LC_NUMERIC category. > 2] @Eli: You wrote > > > > The problem with that, of course, is that not every supported > > > platform can dynamically change the locale, let alone do that > > > efficiently. > > I have no idea to what actual supported platform you're referring. GNU/Linux is the only one I know of that can efficiently switch locales dynamically (and even that in recent versions of libc, AFAIR). > > > Text processing in Emacs is generally separate from the current > > > locale's rules, > > > ... > > > So passing a locale argument to functions that produce output, > > > with the intent to request some behavior to be tailored to that > > > locale, is the only reasonable way to have this kind > > Agreed. My input here is that there should be clear documentation of > how to retrieve a value for that argument from a buffer's context, > (maybe the same way that flyspell does?). Sorry, I don't see the relevance. I was talking about calling functions, so how does some buffer enter this picture? Buffers don't have anything to do with the locale used by library functions called by Emacs.