As a non-native English speaker, I find it utterly confusing to read text containing figures like "1,234 m", which in English means 1234 m while for a person used to read e.g. French or German (person's native language) it'll mean 1234 mm at first, only to be re-read to reinterpret correctly.
There seems to exist a cure for this: according to Wikipedia,
Since 2003, the use of spaces as separators (for example: 20 000 and 1 000 000 for "twenty thousand" and "one million") has been officially endorsed by SI/ISO 31-0 standard, as well as by the International Bureau of Weights and Measures and the International Union of Pure and Applied Chemistry (IUPAC), the American Medical Association's widely followed AMA Manual of Style, and the Metrication Board, among others.
But, as the posts on StackExchange contain lots of numbers with comma as digit grouping symbol, I'm reluctant to change them to narrow spaces when editing, because I worry that this may be regarded as a question of style, although I suppose using spaces will help non-native-English audience avoid mistaken reading of the numbers — especially 4- to 6-digit long ones, where there's only one comma (two or more commas is a hint already that it's not integer-fraction separator). So far I've approached this conservatively, only fixing numbers lacking integral part in a decimal number (like
.1345 instead of
0.1345) by prepending zeros to them, to make it more obvious that there's a point before the digits.
My question is, is it acceptable, when fixing formatting of a post, to replace commas in numbers to narrow no-break spaces (U+202F)? Or are there any good reasons why I shouldn't do it? Does the answer to this depend on the site (e.g. Physics.SE vs English.SE)?