Issue 95958 - export CVS: either provide user option for record delimiter or default to CRLF
Summary: export CVS: either provide user option for record delimiter or default to CRLF
Status: CLOSED DUPLICATE of issue 82952
Alias: None
Product: Calc
Classification: Application
Component: save-export (show other issues)
Version: OOo 3.0
Hardware: Unknown All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: spreadsheet
QA Contact: issues@sc
Depends on:
Reported: 2008-11-07 12:46 UTC by zhangweiwu
Modified: 2009-07-22 06:55 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description zhangweiwu 2008-11-07 12:46:02 UTC
According to RFC 4180 CRLF is the record delimiter for CSV format (there is no
second option to use only LF). This is based on the well understanding of more
number of current application that takes CSV can accept CRLF then those support
CR or LF.

Current text delimiter seems to be based on the OS's default. A Linux user may
wish to prepare a CSV file for a Windows user who happen to use a program that
only accept CSV file line-separated with CRLF. In such situation the user is
stuck. He have to use posix command "tr" but he probably isn't able to or prefer
not to use commandline.

A second reason to use CRLF for record separator is it gives user possibility to
work with data with line-based software, e.g. awk. One awk user can easily set
RS (record separator) to CRLF and not worrying about logics to handle table
cells containing linefeed (a cell can safely contain either CR or LF but not
together). Since the user is actually using awk, he is more likely using Linux
or MacOS, which defaults to CR or LF for EOL (but not both), then this user is
going to enjoy the CRLF as record separator.

either provide user option for record delimiter (always have CRLF selected by
or always use CRLF for export CSV files.
Comment 1 chl207 2008-11-21 09:26:47 UTC
In OOo3.0RC4 On WinXP,the issue exists.
Comment 2 peter.junge 2009-07-22 06:48:07 UTC

*** This issue has been marked as a duplicate of 82952 ***
Comment 3 peter.junge 2009-07-22 06:55:29 UTC