Re: built-in printf %f parameter format depend on LC_NUMERIC
From:
Léa Gris
Subject:
Re: built-in printf %f parameter format depend on LC_NUMERIC
Date:
Fri, 12 Jul 2019 18:46:43 +0200
User-agent:
Telnet/1.0 [tlh] (PDP11/DEC)
Le 09/07/2019 à 22:02, Chet Ramey écrivait :
These are up to the system's strtol/strtod. I don't know of too many
strtol implementations that use the thousands separator and numeric
grouping.
Chet and you other Bash maintainers or contributors dudes:
I can foresee the implications and blockages even lightly considering
the possibility to align the Bash's built-in printf behavior with the %f
argument with the sibling GNU Coreutils printf implementation.
Anyway, I hope this topic to remain a place for sane discussions about
the implications of Bash's printf implementation for numerical data
interoperability while allowing display and printout to user locale format.
Because it help myself in a positive way, I'd like to share my free
software contribution with a small lcnumconv.sh library I made available
here:
The README exposes the incentives behind this library/stand-alone
command, that may shed some light on how the Bash's printf
implementation of the %f format can be an issue.
Be glad if it can helps in some way.
Do what the F** you want with it :)
--
Léa Gris
signature.asc Description: OpenPGP digital signature