Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data Schema with characters incompatible with ascii #47

Open
Civity-NL opened this issue Oct 15, 2019 · 1 comment
Open

Data Schema with characters incompatible with ascii #47

Civity-NL opened this issue Oct 15, 2019 · 1 comment

Comments

@Civity-NL
Copy link

Overview

The Data Schema JSON will throw an error if it includes characters not compatible with ascii.
This happens due to the use of Swedish characters like "Ö" and "Ä".

validation

This is the line of code where it happens. I made a quick workaround by replacing it with:

descriptor = json.loads(value.encode('utf-8'))

Just wanted to get some feedback on how to approach this, if there should be somewhere an option to declare the encoding of the file? Or you want a PR with this work around?


Please preserve this line to notify @amercader (maintainer of this repository)

JVickery-TBS pushed a commit to JVickery-TBS/ckanext-validation that referenced this issue Jul 23, 2024
@KatiRG
Copy link

KatiRG commented Jul 27, 2024

I am also facing a similar issue that ckanext-validation is stripping french accents from the header names. We previously implemented a fix in xloader here: loader.py, but it seems that ckanext-validation does not go through the load_csv() function of xloader where the unidecode option can be checked.

Can you please advise where in ckanext-validation such a check can be made to preserve accents in the headers? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants