-
Notifications
You must be signed in to change notification settings - Fork 11
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
[frontend] Issue with encoding of the title #215
Comments
@Mikanebu can we guess encoding in frontend? |
@zelima let's give a try |
… decode on frontend using descriptor.encoding - refs datopian/frontend#215
… decode on frontend using descriptor.encoding - refs datopian/frontend#215
#45) * [descriptor-encoding][xs]: added encoding to Dataset class, so we can decode on frontend using descriptor.encoding - refs datopian/frontend#215
This should be fixed once frictionlessdata/datapackage-py#211 is merged and deployed. |
@Mikanebu can you please test it now and close if fixed |
@anuveyatsu tested, it is not the correct title. I assigned |
FIXED, now we handle encoding descriptor as well. Published test dataset worked fine https://datahub.io/Mikanebu/hello-world-4 |
Issue reported here datopian/datahub-qa#37
See https://datahub.io/joelgombin/ville_vitry_subventions_2017: the title of the page - which was passed by the CLI tool - has encoding issue, whereas the previewing of the CSV resource is fine.
Acceptance criteria
Tasks
Analysis
The reason behind this problem is that browser by default using
utf-8
encoding to decode data which comes originally from specstore. Tried to configure amazon s3 bucket, but unfortunately, it did not help by assigning metadataencoding: utf-8
, but decoding withiso-8859-9
which translatesRéunion
toRéunion
.https://datahub.io/Mikanebu/test5
As a result, we cannot encode using
utf-8
when it decoded using different encoding.We decided that encoding work should be handled on frontend side if we pass encoding from the backend. For example, if you take a look on GitHub files.
Preview of data looks fine: https://github.com/frictionlessdata/test-data/blob/master/files/csv/encodings/iso8859.csv
However, the original data is different: https://raw.githubusercontent.com/frictionlessdata/test-data/master/files/csv/encodings/iso8859.csv
Tested by passing encoding
latin1
to the frontend manually and it worked.The solution would be the following:
The text was updated successfully, but these errors were encountered: