-
Notifications
You must be signed in to change notification settings - Fork 63
How to detect the encoding of the loaded file before displaying data ? #82
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
Comments
@dimitri-hoareau-WEL Would you like to check data of the file is UTF-8 or ISO-8859-1 before upload? |
Yes ! I wanted to know if it's possible to do that ? |
Hi! I am having the same issue, is this being worked on? |
I may send a pull request in the coming weeks! |
@exaucae would you mind sharing any update? I'm having this issue as well |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi !
I had a problem for displaying special characters with CVSReader due to csv files which were encoded as ISO-8859-1 instead of utf-8 (ex : Pyr�n�es-Atlantiques )
By adding :
in my code it's working, the browser can now read special characters without problems. But the new problem is when loading a file encoded in utf-8, the characters are not displayed properly (ex : Pyrénées-Atlantiques )
My problem is that I am working with clients who do not use the same encoding for their csv files. Some clients use "utf-8", others use "ISO-8859-1". And I can not know in advance what will be the encoding of the file used.
Here is my code :
I use redux and the "encoding" variable is in the state with this default value :
With this solution, the client must load the file a first time to update the state with the correct value of "encoding", and load the file a second time to display data with the correct encoding.
Is there a native CSVReader's method that allows you to detect the encoding of the loaded file before displaying the data ?
Thank you very much for your help
Dimitri
The text was updated successfully, but these errors were encountered: