-
Notifications
You must be signed in to change notification settings - Fork 2
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
Bad character encoding when exporting data #20
Comments
@jamiefolsom Is this something you can fix or it's someone else job? Thanks for the info! |
Hi @blirette -- I believe this is due to excel not parsing the correct characters correctly. It appears to me that the text editor in the second case is handling that file properly, but that excel is not. It may be possible to force Excel to treat the file as UTF-8. Does that make sense? |
@jamiefolsom We need to generate a file that gets interpreted correctly across all apps. It must be a header problem in the file generated or something like that. |
Can you fix this @jamiefolsom or it'll take a lot of time? I can live with that if you tell me the problem is deeply rooted in the encoding of the data in the database or it's lost somewhere between all the data transfers. I just hope this won't get worst once we separate the data backend from the frontend. Lemme know what you think. Thanks! |
@jamiefolsom Could you enlight me on this? Thanks! |
This is still a problem. The CSV file isn't displayed properly of Sara's version of Excel too. |
Character encoding doesn't seem to work properly when exporting data. It might be related to the file metadata too since Excel doesn't seem to show accentuated characters properly, but another app like TexWrangler display them properly (see screenshots).
This causes problems to non "tech-savy" users.
Microsoft Excel 2015.29.1 for Mac
TextWrangler 5.5.2
The text was updated successfully, but these errors were encountered: