Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestions for Briefcase CSV #217

Open
GoogleCodeExporter opened this issue Jul 23, 2015 · 1 comment
Open

Suggestions for Briefcase CSV #217

GoogleCodeExporter opened this issue Jul 23, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link
Contributor

From Manna Energy

null fields show in the briefcase csv as nothing so you end up with a bunch of 
commas in a row when there is a null value from an optional field that was 
skipped. This, combined with the fact all the other fields with values have 
quotation marks, makes it difficuilt to parse the csv via delimiters. Cant use 
commas because those can be in the strings as well, but you cant use "," either 
because the null fields are lacking quotes. We had to resort to some craftyness 
to properly delimit the csv. 

Original issue reported on code.google.com by [email protected] on 20 May 2011 at 10:13

@GoogleCodeExporter
Copy link
Contributor Author

There's actually an RFC describing CSV file formats.  
The complaints are a critique of the CSV file format, which Briefcase adheres 
to:

http://tools.ietf.org/html/rfc4180

Changing to documentation.

Original comment by [email protected] on 30 Jan 2012 at 10:04

  • Added labels: Documentation, Type-Other
  • Removed labels: Type-Defect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant