Re: Quoting text strings for SCV output -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Hi John -

On Thu, 17 Nov 2016 00:06:20 -0500, John Yeung
<gallium.arsenide@xxxxxxxxx> wrote:

On Wed, Nov 16, 2016 at 10:00 PM, Ken Sims <mdrg8066@xxxxxxxxxxx> wrote:

The standard for CSV text fields [...]

There isn't a single standard for CSV. The closest thing to a standard
is probably Excel-flavored CSV (which is what you describe), but only
because Excel is so common. It would be somewhat like saying backslash
is the standard path separator character, because Windows is more
common than anything else.

The thing is, OP already established from his very first post that
Excel-flavored CSV doesn't meet his requirements.

While there is not complete consistency, the information that I used
when I wrote my CSV processing many years ago (for attachment building
for a proprietary email system that I wrote) is from RFC4180, which is
the closest thing to an actual standard that I'm aware of.

https://www.ietf.org/rfc/rfc4180.txt

Ken
Opinions expressed are my own and do not necessarily represent the views
of my previous employers or anyone in their right mind.

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.