Have you considered using File > File Options... > Text > Always use file's saved settings?
We have tried but there is no difference.
We have seen similar issues with formats of dates and numbers when I use a file created on a Dutch system (where we use , as a decimal separator) on a US system even if they use local settings.
For us the solution was to create a clone of the database and open it on the US machine so it stored the US settings, so that might be the solution for you.
You can also try to export and import the file to a FM file instead of csv, then FM server does not have to read from a textfile and does not have to translate the text into numbers and dates
Hope that helps
yes. FileMaker Server runs everything with US formats. Major pain, but it's been that way for years.
Re. workarounds, you basically need to know if the script is running on the server or in a client and deal with the imports/exports accordingly. You can do your export from a layout that's US formatted and export applying the layout styles on export. Then when you import it will come in correctly. You do end up with two branches of code doing exactly the same thing with one minor variation which is not ideal as it increases the risk of bugs.
best thing to do is report it as a bug and submit a feature request to change the behaviour. Having said that - i've not tested to see if 14 has fixed this.