-
Notifications
You must be signed in to change notification settings - Fork 26
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
page.raw_data not get converted to utf-8 #5
Comments
Thanks @buger, we'll be sure to address this before the first non-beta release. |
It does seem to me like this shoud be handled by replacing |
Hmm, on second thought, it seems like and gollum and gollum-lib already use
Not sure if it should be changed in any of those places. |
Exactly. Which is why I wanted to know which call specifically was causing trouble. :) |
Agree. Ping @buger, can you help us reproduce your issue/point to the |
sure, I'll try to re-create test case |
@buger Any luck re-creating a test case? |
Sorry, but I'm not working on this project anymore On Wednesday, 31 August 2016, Bart Kamphorst <notifications@github.com
https://goreplay.org - test your system with real data |
This should be resolved in 5.x, at least utf-8 contents are displaying fine. Closing because of no further info on how to reproduce. |
After switching to rugged adapter i started getting
incompatible character encodings: ASCII-8BIT and UTF-8
errors and found that page.raw_data is returned in ASCII-8BIT encoding (was utf-8 using grit). I guess this should be converted inside adapter.The text was updated successfully, but these errors were encountered: