How to choose delimiter for CSV? [closed]

asked 2014-02-09 18:20:08 +0200

adam r gravatar image

updated 2015-08-29 21:27:53 +0200

Alex Kemp gravatar image

What is the recommended way to choose the delimiter used for CSV export with LO Calc?

My problem is that my spreadsheet is being saved with tab delimiters while my downstream program expects comma-delimiters. This seems to have somehow become the default for my file, which is non-intuitive behavior for a "comma separated file". This may be a bug. I am using build on Fedora.

Here's the behavior that I've identified, but they do not suggest a straight-forward way of handling this issue:

First, here's the official description:

In my experience, the first time I save a file as CSV, I am given the "Export Text File" prompt, and I can select whatever delimiter I want (confirmed with gEdit). However, if I open the file to edit it, I do not see that prompt the next time that I save. For subsequent saves, tabs are used, even if I had used commas originally.

I think this may be connected to the "Text Import" dialog choices. If I import the text with multiple delimiters selected, then the next time it is saved with tabs. However, if I deselect the non-comma delimiters, then it saves with comma delimiters. My impression is that the default is to import with comma, tabs, and semicolons as delimiters.

If I want to specify the delimiters (again), I've found that I can select the "Edit Filter Settings" checkbox on the save dialog. After clicking OK and then confirming that I do really want to save the file with the selected name and format, the "Export Text File" prompt will show up again. My guess is that this is the recommended way to select the delimiter, though I found this to be non-intuitive and clumsy.

Is there a better (more convenient) way? Is this a bug?

thanks in advance.

edit retag flag offensive reopen merge delete

Closed for the following reason duplicate question by oweng
close date 2014-02-10 00:52:05.785883


This is basically a dup of . I tried to close but could not. I contributed my description as an answer to the other question. I think my question/title is more explicit about the nature of the problem and would therefore be easier to find.

adam r gravatar imageadam r ( 2014-02-09 18:27:03 +0200 )edit

Thanks for indicating this Adam. I will close this question as a duplicate.

oweng gravatar imageoweng ( 2014-02-10 00:51:28 +0200 )edit