3 ms·
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 form
by barrkel 12y ago
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...
- mschuster91 12y ago> Likely the next invalid format we'll have to parse is PDFs containing tables... cough people doing e-invoicing with pdf's...
- Mister_Snuggles 12y ago> 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...