Ultimately I guess my Excel issues probably concern a more global desire for predictability of CSV format across products, which will probably seem mundane to you. Not that MS is the only player I have run into with these issues in the not-daily experiences I've had with this.

The Excel '97 on my laptop will export everything separated by a comma, unless there's a comma within the field (cell), whereupon it exports that cell (and only that cell) with double quote delimiters. It also offers me no controls to set preferences for this export type.

OTOH, my memory of it is that MS's FoxPro products seem to prefer to use double quote delimiters on all fields, Outlook exports with double quotes on all fields, but Outlook Express seems to export with commas only, just as examples. go figure. The other side of this is for me has been that over the years, various products I would use to import a file expected a CSV file to be in one or another structure (double quotes, no quotes, etc.)

StarOffice products offers chooices on all the characteristics of these exports, which I of course admire and wish other products did the same.

In reply to Re: Re (tilly) 6: csv output by tjh
in thread csv output by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.