Work around extra separators in buggy CSVs
Reported by Virgil Dupras | March 17th, 2012 @ 03:33 PM
Some CSV are malformed and contain unescaped separator characters that aren't separator (comma for example). It would be nice if moneyGuru could work around these cases. I'm not sure how exactly. Maybe by enlarging the table to accomodate buggy lines (that's what Numbers does when you open such a CSV in it)? So we'd have buggy data, but at least the user would have an idea of what's happening instead of wondering why moneyGuru is telling him that the CSV can't be opened.
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Virgil Dupras