rfc4180

According to RFC 4180 : ...the presence or absence of the header line should be indicated via the optional "header" parameter of this MIME type... So, does that mean the correct string is: text/csv; header Or perhaps: text/csv; header=true Or something else? hobbs The "header" parameter indicates the presence or absence of the header line. Valid values are "present" or "absent". So if you use that parameter, the full MIME type would be text/csv; header=present or text/csv; header=absent . 来源： https://stackoverflow.com/questions/15457752/proper-syntax-for-optional-header-parameter-for-text-csv

I have a bunch of CSV data that I need to load into a MySQL database. Well, CSV-ish, perhaps. ( edit : actually, it looks like the stuff described in RFC 4180 ) Each row is a list of comma-separated doublequoted strings. To escape any doublequotes that appear within a column value, double doublequotes are used. Backslashes are allowed to represent themselves. For example, the line: "", "\wave\", ""hello,"" said the vicar", "what are ""scare-quotes"" good for?", "I'm reading ""Bossypants""" if parsed into JSON should be: [ "", "\\wave\\", "\"hello,\" said the vicar", "what are \"scare-quotes\"

I am aware of fputcsv, but according to this "wontfix" bug fputcsv does not correctly escape input, and its behavior will not be fixed for compatibility reasons. I would prefer an implementation that is compliant with RFC 4180 so Excel and LibreOffice can open it in all cases. I've tried googling for a library that does this correctly, but there doesn't seem to be a consensus on a decent third party library, instead commonly suggesting the defective fputcsv. I could always roll my own, but I'd prefer not to reinvent the wheel if at all possible. Charles It seems that every library out there