From: Eli Zaretskii <eliz@gnu.org>
To: Maxim Nikulin <manikulin@gmail.com>
Cc: boruch_baum@gmx.com, emacs-devel@gnu.org
Subject: Re: CSV parsing and other issues (Re: LC_NUMERIC)
Date: Fri, 11 Jun 2021 21:04:51 +0300 [thread overview]
Message-ID: <83h7i49t18.fsf@gnu.org> (raw)
In-Reply-To: <ce36cd3b-dd9b-9219-afbe-84a9bdd8f2b8@gmail.com> (message from Maxim Nikulin on Fri, 11 Jun 2021 23:58:24 +0700)
> From: Maxim Nikulin <manikulin@gmail.com>
> Date: Fri, 11 Jun 2021 23:58:24 +0700
> Cc: boruch_baum@gmx.com
>
> On 10/06/2021 23:57, Eli Zaretskii wrote:
> >> From: Maxim Nikulin Date: Thu, 10 Jun 2021 23:28:59 +0700
> >
> > For processing CSV, if there's a need to know whether the
> > locale uses the comma as a decimal separator, we could
> > indeed extend locale-info. But such an extension is almost
> > trivial and doesn't even touch on the significant problems
> > in the rest of the discussion.
> >
>
> You forgot `setlocale(LC_NUMERIC, "C")', didn't you?
No, I didn't. Adding a call to setlocale to locale-info, even if we
want to add an argument for the caller to control the locale, is
trivial.
> > Here's a trivial example:
> >
> > (insert (downcase (buffer-substring POS1 POS2)))
> >
> > Contrast with
> >
> > (insert (downcase "FOO"))
>
> Either `set-text-properties' should be called on "FOO" before passing it
> to `downcase'
Which property will help here? we don't have such properties. they
need to be designed and implemented.
> or `locale-downcase' with LOCALE first argument should be
> added.
How would you implement locale-downcase? Are you familiar with how
Emacs case tables work?
And even if we had locale-downcase, which locale would you pass to it
in any given use case?
Please note that I'm not saying these issues cannot be solved -- they
can. I'm saying that designing them requires non-trivial thought,
something we didn't yet do.
next prev parent reply other threads:[~2021-06-11 18:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 23:36 CSV parsing and other issues (Re: LC_NUMERIC) Boruch Baum
2021-06-07 12:28 ` Eli Zaretskii
2021-06-08 0:45 ` Boruch Baum
2021-06-08 2:35 ` Eli Zaretskii
2021-06-08 15:35 ` Stefan Monnier
2021-06-08 16:35 ` Maxim Nikulin
2021-06-08 18:52 ` Eli Zaretskii
2021-06-10 16:28 ` Maxim Nikulin
2021-06-10 16:57 ` Eli Zaretskii
2021-06-10 18:01 ` Boruch Baum
2021-06-10 18:50 ` Eli Zaretskii
2021-06-10 19:04 ` Boruch Baum
2021-06-10 19:23 ` Eli Zaretskii
2021-06-10 20:20 ` Boruch Baum
2021-06-11 6:19 ` Eli Zaretskii
2021-06-11 8:18 ` Boruch Baum
2021-06-11 16:51 ` Maxim Nikulin
2021-06-11 13:56 ` Filipp Gunbin
2021-06-11 14:10 ` Eli Zaretskii
2021-06-11 18:52 ` Filipp Gunbin
2021-06-11 19:34 ` Eli Zaretskii
2021-06-11 16:58 ` Maxim Nikulin
2021-06-11 18:04 ` Eli Zaretskii [this message]
2021-06-14 16:38 ` Maxim Nikulin
2021-06-14 17:19 ` Eli Zaretskii
2021-06-16 17:27 ` Maxim Nikulin
2021-06-16 17:36 ` Eli Zaretskii
2021-06-10 21:10 ` Stefan Monnier
2021-06-12 14:41 ` Maxim Nikulin
-- strict thread matches above, loose matches on Subject: below --
2021-06-02 18:54 LC_NUMERIC formatting [FEATURE REQUEST] Boruch Baum
2021-06-03 14:44 ` CSV parsing and other issues (Re: LC_NUMERIC) Maxim Nikulin
2021-06-03 15:01 ` Eli Zaretskii
2021-06-04 16:31 ` Maxim Nikulin
2021-06-04 19:17 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h7i49t18.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=boruch_baum@gmx.com \
--cc=emacs-devel@gnu.org \
--cc=manikulin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).