On 3/1/23 4:18 AM, Brian Beezley wrote:
On Wed, Mar 1, 2023 at 02:25 AM, <btomek@...> wrote:
Full s1p in attachment.
I'm curious why your Touchstone files use commas rather than periods in decimal numbers. The utilities and programs I write used to check for commas and replace them with periods, but to simplify the code I dropped that check after not encountering any files with commas for a long time. None of that software will work with your files. This includes a utility that checks for |Sij| > 1, which is invalid but occurs in several of your files.
Some software is localized, and when you put out a number, by default it uses comma as the "decimal point". In particular the various MS Visual whatevers can do this for dialogs. What's sort of pernicious is that by default, if you bought and installed Windows in the US, it's turned off, so even if you set a different region, it stays "." for decimal point; but if you bought and installed Windows somewhere else, it's turned on, and the decimal separator (and other stuff) is localize to the region setting.
I've also seen this for thousands separator (. in some EU countries, , in US). And, of course for dates (MM-DD-YY vs YY-MM-DD)
it's been a number of years (~5) since I did any significant coding specifically for the Windows platform, so it might be better now, but....
And BTW, packages like QT (on all platforms) have similar issues. They try to make localization easy, but you always wind up with a heterogenous combination.
(I've been caught by this before..)
