Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15106
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: built-in printf %f parameter format depend on LC_NUMERIC |
| Date | 2019-07-09 16:02 -0400 |
| Message-ID | <mailman.715.1562702603.2688.bug-bash@gnu.org> (permalink) |
| References | <5d24be33.1c69fb81.59c43.fe4dSMTPIN_ADDED_BROKEN@mx.google.com> <a212b38c-914d-dda6-8d22-e9039063768e@case.edu> <6468b45e-5b4a-8edf-4ab8-0838843beaaf@noiraude.net> <b6f65b6b-1487-0c46-6530-fa6d700ff1ca@case.edu> |
[Multipart message — attachments visible in raw view] - view raw
On 7/9/19 3:39 PM, Léa Gris wrote: > I note that Bash's built-in printf %f or %d does not honour LC_NUMERIC > thousands_sep=" " when dealing with integers. > > $ printf '%f\n' '1 000 000' > bash: printf: 1 000 000: nombre non valable > 1,000000 > > locale -ck thousands_sep > LC_NUMERIC > thousands_sep=" " > > $ printf '%d\n' '1 000 000' > bash: printf: 1 000 000: nombre non valable > 1 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. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: built-in printf %f parameter format depend on LC_NUMERIC Chet Ramey <chet.ramey@case.edu> - 2019-07-09 16:02 -0400
csiph-web