javascript - toLocaleString not working on numbers less than 10000 in all browsers - Stack Overflow

admin管理员组

文章数量:1198178

I'm working on an application, that displays numbers according to the user's configuration. Everything works as expected, except when I try with numbers less than 10000,in Chrome, with the following locale: "es-AR". Any ideas?

Chrome:

Firefox:

Edge:

console.log( (10000).toLocaleString("es-AR") );
console.log( (9999).toLocaleString("es-AR") );
console.log( (9999).toLocaleString("en-US") );

I'm working on an application, that displays numbers according to the user's configuration. Everything works as expected, except when I try with numbers less than 10000,in Chrome, with the following locale: "es-AR". Any ideas?

Chrome:

Firefox:

Edge:

console.log( (10000).toLocaleString("es-AR") );
console.log( (9999).toLocaleString("es-AR") );
console.log( (9999).toLocaleString("en-US") );

• javascript
• locale

Share Improve this question Follow edited Aug 23, 2019 at 14:18 Lee Taylor 7,9741616 gold badges3737 silver badges5353 bronze badges asked Aug 23, 2019 at 14:12 JS5JS5 77977 silver badges1717 bronze badges

Add a comment  | 

3 Answers 3

Sorted by: Reset to default 16

This is the intended behaviour for Spanish locales according to the latest CLDR data. Specifically the "Minimum Grouping Digits" are set to 2 according to the CLDR survey tool.

This means that that the grouping separator is only used when there would be 2 or more digits before it.

Apparently Firefox and Edge either uses an older version of that data or don't have support for that field yet.

The feature was introduced in CLDR 26, which was released in 2014, but enhancements like this take quite a while to make their way through the software stack.

Minimum Grouping Digits for Spain's Spanish language, according CLDR, is indeed two.

Full language specifications can be found in GitHub.

Interestingly enough, using always a minimum of two grouping digits is in conflict with the RAE rules. They state that this recommendation doesn't apply to all contexts, mentioning as specific exceptions accountancy and any context where it can involve a security risk.

Given that the spec forces this behavior and that real-life experience is that this is sometimes reported as a bug that needs fixing, here is a simple workaround as requested by the original poster. It's as dirty as detecting four integer digits and adding the thousands separator manually (and could be done many better ways).

var decimals=2;

value=value.toLocaleString('es', {minimumFractionDigits: decimals, maximumFractionDigits: decimals});

//fix spanish thousands separator for <10.000
if(value.indexOf(',')==4 || (decimals==0 && value.length==4)){
    value=value.substr(0,1)+'.'+value.substr(1);
}

本文标签： javascripttoLocaleString not working on numbers less than 10000 in all browsersStack Overflow