For the record there is currently no such thing as a standard CSV format.
If you are using Microsoft Excel, it will encapsulate each "cell" of data in quotes, instead of escaping the commas. However, what if the cells have quote marks? I suppose they would need to be escaped if using that format. I found the following "guide" to CSV online.
Considerations When Exporting CSV
The biggest differences are in how these three characters are handled.
- Embedded double quotes in fields.
- An escape character is sometimes used to introduce a double quote, or in place of it.
- Embedded line-feeds in fields.
- This one is also escaped sometimes. Often like in C ("\n")
- Embedded commas in fields.
- Again, an escape character is sometimes used in place of the comma
Theoretically, if you could avoid exporting any fields that include these characters you would greatly improve the chances that your CSV file could be read by variations.
Is it worth reducing your application's functionality or convenience? No. But if the existence of these characters is entirely superfluous, you might consider taking them out.
Take your pick. I picked one format. There are others.
Blessings,
~Polyglot~
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
