I did see that later in the doc, the author says section 2 is
"an attempt at a common definition".
Some may not realize that csv format was around over a decade before the
invention of personal computers, Windows, and products like Excel.
Jim Franz

----- Original Message ----- From: "Narayanan R Pillai" <strqst400@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, December 04, 2013 9:12 PM
Subject: Re: SQL output to csv


John,

You are correct about the "at all" usage. Under normal circumstances,
Excel does not produce CSVs with double-quotes, in the cases where
special characters are present it does do that. I think the RFC should
reflect that.

However, the default behaviour is not RFC compliant.

Pillai


On 12/04/2013 05:11 PM, John Yeung wrote:
On Wed, Dec 4, 2013 at 4:30 PM, Narayanan Pillai <strqst400@xxxxxxxxx> wrote:
I know this is not the right forum to discuss RFCs, but I interpreted
that comment to mean - don't expect excel produced CSVs to look
like this spec. From experience, excel does not produce CSVs with
double quoted fields
The RFC states that "some programs, such as Microsoft Excel, do not
use double quotes at all". But Excel DOES use double quotes whenever
the data contains commas, double-quotes, or newlines.

John

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].