Hi Stefan, the locale can have an impact on how numbers are parsed with certain kinds of parsing functions.

Somewhere in there is a bug that numbers are being parsed with a locale-specific handler when it should not be.

Thank you for posting your settings and for testing with altered locale to narrow down the problem, that should let me reproduce it over here and investigate a fix.

- Michael

It is kind of weird that other files did work ok for you though. Anyway tomorrow I will investigate and try to see what's going on there.

- Michael

.Deleted irrelevant post.

Hi Stefan, I've been investigating this import point file problem today and it seems to be a bug pretty deep in the scripting system involving conversion of string values to number values. It's also not unique to the Mac version, it happens on the Windows version too.

I'm working on a fix to the script engine itself for the next v3 release, but in the meantime here is an updated ImportPointFile plug-in which has a slight modification which will avoid triggering this particular bug, this version should work for you with your original locale settings, please let me know if it still does not.

Thanks,
- Michael

Hi Michael,

works fine now! Thank you very much for the quick fix, much appreciated!

Regards
Stefan