Skip to content
This repository has been archived by the owner on Nov 28, 2024. It is now read-only.

When download the "Standardised CSV"; give option to automatically fix encoding to UTF-8 #267

Open
leowmjw opened this issue May 20, 2016 · 2 comments

Comments

@leowmjw
Copy link

leowmjw commented May 20, 2016

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

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
@quadrophobiac
Copy link
Contributor

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

@quadrophobiac
Copy link
Contributor

This issue was moved to Data-Liberation-Front/csvlint.rb#205

@quadrophobiac quadrophobiac reopened this Jul 7, 2017
@quadrophobiac quadrophobiac changed the title Unclear where validation fails and not automatically fixing encoding When download the "Standardised CSV"; give option to automatically fix encoding to UTF-8 Jul 7, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants