Unclear where validation fails and not automatically fixing encoding

[quadrophobiac]

From @leowmjw on May 20, 2016 12:51

Have reviewed #182; would like to request the ability to know where and why the validation fails; even when there is no schema provided.

• Data: http://leowmjw.github.io/selangor_adun_2016/data/573ef1d66373766db400013b.html
• Validation Failure: http://csvlint.io/validation/573ef4906373766db400013c
• Output:

Schema problem: Inconsistent value in column 13

The data in column 13 is inconsistent with others values in the same column.

Schema problem: Inconsistent value in column 14

The data in column 14 is inconsistent with others values in the same column.

Context problem: Incorrect Encoding

Your CSV appears to be encoded in ASCII-8BIT. We recommend you use UTF-8.

Suggestion:

1. Should show which row(s) of data causing the validation failure (and the reason), even when no provided schema
2. When download the "Standardised CSV"; give option to automatically fix encoding to UTF-8

Copied from original issue: Data-Liberation-Front/csvlint.io#267

[quadrophobiac]

Hi @leowmjw - appreciate my reply is very cold coffee. I'm working with the ODI to support their Open Source Software and I'm going through the issues on the repositories. I think the issue you've flagged is better broken into two distinct tickets.

Suggestion 1 seems a better fit for the CSVlint library that powers the service, so Ill open an issue against that.
I think we can make suggestion 2 the body of this issue