From: Eli Zaretskii <eliz@gnu.org>
To: Maxim Nikulin <manikulin@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: CSV parsing and other issues (Re: LC_NUMERIC)
Date: Mon, 14 Jun 2021 20:19:31 +0300 [thread overview]
Message-ID: <83h7i05pp8.fsf@gnu.org> (raw)
In-Reply-To: <sa80ls$iev$1@ciao.gmane.io> (message from Maxim Nikulin on Mon, 14 Jun 2021 23:38:19 +0700)
> From: Maxim Nikulin <manikulin@gmail.com>
> Date: Mon, 14 Jun 2021 23:38:19 +0700
>
> >> 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.
>
> I would avoid such manipulations and the reason is not efficiency of
> particular implementation.
But we already do that in locale-info, for locale categories other
than LC_NUMERIC.
> >> > 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.
> Let's name it "locale". Its value is some object that represents either
> a "solid" locale such as de_DE or combined LC_NUMERIC=en_GB +
> LC_TIME=de_DE + default fr_FR. Data required for particular operations
> may be loaded on demand.
How do you associate such an object with text of a buffer or a string
such that different parts of the text could have different "locales"
(as required for a multi-lingual editor such as Emacs)?
> > How would you implement locale-downcase? Are you familiar with how
> > Emacs case tables work?
>
> No, I am not familiar with Emacs internals dealing with case conversion.
> I already wrote I am even unaware how to properly handle Turkish. For
> the scripts I am familiar with, it is enough to have default table for
> normalizing and conversion. I can admit that sometimes conversion may
> depend on language and the language can not be determined from code
> point. In such cases I expect additional override table that has higher
> priority than the default one.
>
> > And even if we had locale-downcase, which locale would you
> > pass to it in any given use case?
>
> I already mentioned responsibility chain: explicit value or set of
> overrides passed by user, text property for particular span of
> characters, buffer-local variables, global environment variables. Locale
> may be instantiated from its name "it_IT". Convenience functions to
> obtain locale at point likely will be useful as well. (Actually I am
> assuming number parsing-formatting rather than case conversion.)
What you describe doesn't exist, not even in its design stage. We are
back where we started: I said at the very beginning that this
infrastructure is missing. It is futile to discuss solutions which
rely on infrastructure that doesn't exist.
next prev parent reply other threads:[~2021-06-14 17:19 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
2021-06-14 16:38 ` Maxim Nikulin
2021-06-14 17:19 ` Eli Zaretskii [this message]
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=83h7i05pp8.fsf@gnu.org \
--to=eliz@gnu.org \
--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).