4 ms·
Or you could include these regional conventions in the character encoding, so that each file knows how it represent its numbers, and enforce them consistently t
by TuringTest 13y ago
Or you could include these regional conventions in the character encoding, so that each file knows how it represent its numbers, and enforce them consistently throughout applications.
That would be a easy programmatic way to solve the problem, that wouldn't require the whole world to adopt a single standard. But of course it'll never happen, as it would require that all programmers know their shit and follow good practices, when it's much easier to throw the technical debt onto users and let them cope with the problem.
- Aardwolf 13y agoIt would require to adopt a single standard, that is, how to encode that in the character encoding and the files. And it would still not stop someone from in the same browser for example using sometimes one notation, sometimes the other notation, depending on e.g. if they're filling in a form for a European bank, or something related to programming.
- TuringTest 13y agoYou mean, exactly like you do with character encodings for different alphabets?
- TophWells 13y ago>Or you could include these regional conventions in the character encoding, so that each file knows how it represent its numbers, and enforce them consistently throughout applications. So if I open a file in Notepad and type 400,123 (using the comma on my keyboard), what character encoding should that be done with?
- TuringTest 13y agoThe one that Notepad has configured by default in your OS version, unless you choose a different encoding when saving the file.