Bug 151007 - When opening a CSV file, default to CSV-spec-compliant options
Summary: When opening a CSV file, default to CSV-spec-compliant options
Status: RESOLVED DUPLICATE of bug 152336
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.0 all versions
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard: needsUXAdvice
Keywords:
Depends on:
Blocks: CSV-Import
  Show dependency tree / graph
 
Reported: 2022-09-16 19:50 UTC by Eyal Rozenberg
Modified: 2025-01-10 15:55 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eyal Rozenberg 2022-09-16 19:50:45 UTC 
Currently, when opening a CSV file, the parsing dialog has its options set to (IIANM) the last settings for parsing any textual data.

Instead, when opening a CSV file (that is, with a ".csv" extension or with a "text/csv" MIME type) - the settings should correspond to the CSV spec, in RFC 4180. So, for example, only a comma separates records, and the string delimiter is double-quotes (").

The _second_ a later times the same CSV file is opened, this may be relaxed to the previous settings for that file, but perhaps that's a separate bug, so let's start with just the default.

Settings which are orthogonal to the CSV spec should behave... actually, I'm not entirely sure what to recommend here.
Comment 1 Gabriel Masei 2024-03-25 14:47:41 UTC 
Hi Eyal,

Take a look over this improvement: https://bugs.documentfoundation.org/show_bug.cgi?id=160355 

Gabriel
Comment 2 Roman Kuznetsov 2025-01-08 16:07:01 UTC 
Eyal, please look at Comment 1 here, is your enhancement still valid?
Comment 3 Eyal Rozenberg 2025-01-10 15:11:15 UTC 
(In reply to Roman Kuznetsov from comment #2)
> Eyal, please look at Comment 1 here, is your enhancement still valid?

No, I believe it is not. Closing this as fixed by the fix for bug 152336.
Comment 4 Roman Kuznetsov 2025-01-10 15:55:30 UTC 
Thanks

*** This bug has been marked as a duplicate of bug 152336 ***