I think you misunderstood my point which was what's confusing for you may be clear for another, and what's clear for you may be confusing for another so the only winning solution would be 1) no formatting 2) only using "." to separate the decimal part (maybe less confusing?) 3) getting the visitor regional preferences which I won't do.
See my first post on that topic:
Quote
Best would be to use "." (US) or "," for decimal separator, and spaces for number grouping -> "$37 267"
That might give the best result without to much confusion.
https://www.bipm.org/utils/en/pdf/Resol22CGPM-EN.pdf
"declares that the symbol for the decimal marker shall be either the point on the line or the comma on
the line,
reaffirms that ìNumbers may be divided in groups of three in order to facilitate reading; neither dots
nor commas are ever inserted in the spaces between groupsî, as stated in Resolution 7 of the
9th CGPM, 1948."
That might give the best result without to much confusion.
https://www.bipm.org/utils/en/pdf/Resol22CGPM-EN.pdf
"declares that the symbol for the decimal marker shall be either the point on the line or the comma on
the line,
reaffirms that ìNumbers may be divided in groups of three in order to facilitate reading; neither dots
nor commas are ever inserted in the spaces between groupsî, as stated in Resolution 7 of the
9th CGPM, 1948."
You can indeed use "." or ",", but for decimal not for the number grouping. That is where it starts to get confusing
The hashes are a good example: "7,443 MH/s"
Might be good for you, but for a big part of the world that is a really low number
Better "7443 MH/s" or "7 443 MH/s" ("7443.99 MH/s" or "7 443.99 MH/s" are fine, indeed)
For me, it is not a really big thing, but if you can make it more understandable for many people, I think that would be great.