Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15106 > unrolled thread

Re: built-in printf %f parameter format depend on LC_NUMERIC

Started byChet Ramey <chet.ramey@case.edu>
First post2019-07-09 16:02 -0400
Last post2019-07-09 16:02 -0400
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: built-in printf %f parameter format depend on LC_NUMERIC Chet Ramey <chet.ramey@case.edu> - 2019-07-09 16:02 -0400

#15106 — Re: built-in printf %f parameter format depend on LC_NUMERIC

FromChet Ramey <chet.ramey@case.edu>
Date2019-07-09 16:02 -0400
SubjectRe: built-in printf %f parameter format depend on LC_NUMERIC
Message-ID<mailman.715.1562702603.2688.bug-bash@gnu.org>

[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/

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web