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: Thu, 10 Jun 2021 22:23:51 +0300 Message-ID: <837dj1bk1k.fsf@gnu.org> References: <20210606233638.v7b7rwbufay5ltn7@E15-2016.optimum.net> <83a6o1hn9l.fsf@gnu.org> <20210608004510.usj7rw2i6tmx6qnw@E15-2016.optimum.net> <83h7i9f5ij.fsf@gnu.org> <73df2202-081b-5e50-677d-e4498b6782d4@gmail.com> <83eedcdw8k.fsf@gnu.org> <83lf7hbqte.fsf@gnu.org> <20210610180145.staexpqsmqpiv44c@E15-2016.optimum.net> <83a6nxbllz.fsf@gnu.org> <20210610190453.gaq5pqlfbvy4zwmp@E15-2016.optimum.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22297"; 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 Thu Jun 10 21:25:06 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 1lrQIc-0005Y0-HP for ged-emacs-devel@m.gmane-mx.org; Thu, 10 Jun 2021 21:25:06 +0200 Original-Received: from localhost ([::1]:58174 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lrQIb-0001DI-G5 for ged-emacs-devel@m.gmane-mx.org; Thu, 10 Jun 2021 15:25:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42732) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lrQHc-0000Vq-VP for emacs-devel@gnu.org; Thu, 10 Jun 2021 15:24:04 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:34922) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lrQHc-0007Gz-MD; Thu, 10 Jun 2021 15:24:04 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3743 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 1lrQHc-0006PG-AI; Thu, 10 Jun 2021 15:24:04 -0400 In-Reply-To: <20210610190453.gaq5pqlfbvy4zwmp@E15-2016.optimum.net> (message from Boruch Baum on Thu, 10 Jun 2021 15:04:53 -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:270671 Archived-At: > Date: Thu, 10 Jun 2021 15:04:53 -0400 > From: Boruch Baum > Cc: manikulin@gmail.com, emacs-devel@gnu.org > > > That would make the output of 'format' dependent on the current > > locale > > That's the elisp programmer's business, not your responsibilty. What could the Lisp programmer do in this situation? > + Elsip function `format' uses `printf' format specifiers. Only for some of the 'format's capabilities, not for all of them. > + Elisp function `format' doesn't expose two of them. I don't think it's TRT for Emacs to expose locale-dependent features that cannot be controlled from Lisp, sorry. We need to find a better way. For example, there could be a Lisp variable that specifies the group separator character, and then 'format' could use that character when the format spec includes %'. Which means we'd need to implement that in our own code; patches welcome.