tags:

views:

955

answers:

4

Is it possible/legal to somehow encode CR/LF characters into a CSV file?

(as part of a CSV standard?)

If so how should i encode CR/LF?

+10  A: 

Yes, you need to wrap in quotes:

"some value
over two lines",some other value

From this document, which is the generally-accepted CSV standard:

A field that contains embedded line-breaks must be surounded by double-quotes

HTH, Kent

Kent Boogaart
A: 

I don't think it's part of the standard (if there even is one), but you could use standard C-style escaping, i.e. encode \r\n.

Keep in mind, however, that if you do that you should also encode the escape character -- i.e. \ yields \ after decoding.

Randolpho
csv does not use C-style escaping
anon
some csv apps support this form. csv is a regrettably poorly defined standard. Talking Excel csv is (pragmatically) best though which this is not
ShuggyCoUk
+3  A: 

the most common variant of csv out there which is the excel compatible one will allow embedded newlines so long as the field is surrounded by double quotes.

foo,bar,"blah blah
more blah blah",baz

or

foo,bar,"blah blah
more blah blah"

or

"blah blah
more blah blah",baz

are all valid. This mechanism also allows for embedded commas.

Using quotes around textual fields without embedded new lines (or commas) is fine too. If the text itself contains a double quote then mechanism to escape it is to put two together, for example.

foo,bar,"this person said ""blah blah 
more blah blah""",baz

Writing a csv reader that handles this correctly can be tricky (especially if you are relying on regular expressions).

ShuggyCoUk
+1  A: 

Mention has been made here of a standard for CSV. I'd be interested to know more about this - the only standards I'm aware of are

anon
yes, the RFC you link to is the definitive standard. It mentions putting CRLF inside double quotes to escape it. Unfortunately, your point about whatever excel accepts is valid... yet another case of MS trying to subvert standards.
rmeador
thanks for the confirmation
anon
That RFC was created in 2005! Excel has supported CsV for quite a lot longer then that...
ShuggyCoUk