Richard,
You may have a look at the CSVProcessor class. It's capable of handling regional differences in the format, the contents, and even the encoding of CSV files (plus a few other features like import more than 254 columns, or column mapping and filtering, ...).
Source and docs at https://github.com/atlopes/csv
On Fri, Apr 16, 2021 at 2:42 PM Richard Kaye rkaye@invaluable.com wrote:
Throwing this one out to the collective wisdom. We're doing a lot with CSV import/experts these days with our web-based WWC application and are running into issues with regionalization. Here in the US, a "standard" CSV means commas between data elements and double quotes around text elements. But in Belgium, the delimiter is the semi-colon and text elements are not wrapped in double quotes. As best I can tell, Excel determines what format to use by the OS settings and not its own application settings. This makes importing from a CSV a bit of a dance for our Belgian clients as they have to change their regional settings, import the file that was received in US format, and then change their settings back. And, of course, changing region affects date and currency formats. For those of you working with clients from multiple locations where the standards may be different, what strategies do you use to deal with this?
TIA
--
rk
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]