[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CSV parsing and other issues (Re: LC_NUMERIC)
From: |
Boruch Baum |
Subject: |
Re: CSV parsing and other issues (Re: LC_NUMERIC) |
Date: |
Thu, 10 Jun 2021 16:20:45 -0400 |
User-agent: |
NeoMutt/20180716 |
On 2021-06-10 22:23, Eli Zaretskii wrote:
> > Date: Thu, 10 Jun 2021 15:04:53 -0400
> > From: Boruch Baum <boruch_baum@gmx.com>
> > 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?
It's not your responsibilty.
I can say that in the use-case that prompted my request, I'm confident
it will *never* be an issue. I ask format to give me a string and I
display it. End of story. Whether just 99% or 99.99%, the overwhelming
majority of cases will be the same. Your concerns are total non-issues.
> > + Elsip function `format' uses `printf' format specifiers.
>
> Only for some of the 'format's capabilities, not for all of them.
[Commentary: 'Some' isn't a number or a percentage.]
[Commentary: I see all format specifiers supported but the two
requested.]
> > + 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
Then don't make them locale specific. Implement the single-quote
specifier the same way you currently handle the floating-point specifier
'%f', a locale-specific format that has existed in emacs without
complaint since ...
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
- Re: CSV parsing and other issues (Re: LC_NUMERIC), (continued)
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Eli Zaretskii, 2021/06/07
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Stefan Monnier, 2021/06/08
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Maxim Nikulin, 2021/06/08
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Eli Zaretskii, 2021/06/08
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Maxim Nikulin, 2021/06/10
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Eli Zaretskii, 2021/06/10
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Boruch Baum, 2021/06/10
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Eli Zaretskii, 2021/06/10
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Boruch Baum, 2021/06/10
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Eli Zaretskii, 2021/06/10
- Re: CSV parsing and other issues (Re: LC_NUMERIC),
Boruch Baum <=
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Eli Zaretskii, 2021/06/11
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Boruch Baum, 2021/06/11
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Maxim Nikulin, 2021/06/11
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Filipp Gunbin, 2021/06/11
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Eli Zaretskii, 2021/06/11
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Filipp Gunbin, 2021/06/11
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Eli Zaretskii, 2021/06/11
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Maxim Nikulin, 2021/06/11
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Eli Zaretskii, 2021/06/11
- Re: CSV parsing and other issues (Re: LC_NUMERIC), Maxim Nikulin, 2021/06/14