On 6 Oct 08, at 18:00, Frank Peelo wrote: > Marco van de Voort wrote: > > In our previous episode, Frank Peelo said: > > > >>>An additional issue with delimiters in this case is the fact, that "C" in > >>>"CSV" may not always be a comma (or that spreadsheet applications may > >>>expect different characters depending on locale - e.g. semicolons, etc.). > >> > >>CSV is occasionally referred to as something other than "Comma Separated > >>Values". I'm not sure why. > > > > > > Because the comma is a bad separator for countries where the comma is the > > decimal separator, like most of mainland Europe. > > But CSV handles that fine! "12,345","67,890","I paid Ç12,34 for my lunch > and I didn't even get chips!" . .
Well, CSV handles it fine, but the applications don't and that was exactly my point: Opening such a CSV (commas used as delimiters as described above and the whole file named *.csv) with MS Excel running on Windows with e.g. Czech locale, the whole lines end up in one cell. If you want to avoid this behaviour (with MS Excel), you need to use semicolons or start the import explicitly from a previously started MS Excel instance (rather than opening the *.csv file directly by double-clicking it in Explorer or so), because that allows specifying a non-default delimiter (like a comma in this case). Tomas _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
