So You Want to Write Your Own CSV code

Re:So You Want to Write Your Own CSV code by barrkel on Sunday May 25, 2014 @02:52PM (#7797150)

On the other hand, the ability to handle all kinds of input can be a chief selling point of your product.

In my current job, the most common "invalid" CSV format we get is .xlsx files.

So I wrote an .xlsx parser (way, way faster than Apache POI).

Another interesting hiccup to consider is CSV inside individual fields - i.e. recursive CSV. There are various ways to handle this, but in my company's line of business the usual route is to duplicate that line once per CSV element found in the field.

Likely the next invalid format we'll have to parse is PDFs containing tables...

[ Parent | on HN ]

Re:So You Want to Write Your Own CSV code by mschuster91 on Sunday May 25, 2014 @08:53PM (#7798217)

> Likely the next invalid format we'll have to parse is PDFs containing tables...

cough people doing e-invoicing with pdf's...

[ Parent | on HN ]

Re:So You Want to Write Your Own CSV code by Mister_Snuggles on Monday May 26, 2014 @11:15AM (#7800054)

> Likely the next invalid format we'll have to parse is PDFs containing tables...

And after that you will have to parse PDFs containing scans (as images, not text) of pages containing tables...

[ Parent | on HN ]