-
Notifications
You must be signed in to change notification settings - Fork 29
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
Further unicode issues #35
Comments
The Norwegian text supplied by Netflix is: While the english text from the Netflix query is: Netflix is serving up the \u2013 in there https://www.netflix.com/JSON/BOB?movieid= response. |
One thing that might be worth trying, I've seen some unicode on hulu that I've had to encode with 'latin1' rather than 'utf-8' to get displaying correctly.... not sure why, it's coming from xml that explicitly says it's 'utf-8'. |
Here is a bit more information on this problem. |
I've only seen this with u2013 and u2026 (a triple period), and your patch worked fine, so I at least think it's worthy of a PR =) But didn't you just replace the Unicode-in-Unicode with the real Unicode instead of "--"? u2013 is apparently an "En dash" and not strictly a double dash. http://en.wikipedia.org/wiki/Dash#En_dash |
Yeah, I replaced it with the correct unicode. Netflix replaces both u2013 and u2026 with "--". (if you compare the English and Norwegian movie descriptions) I was temped to just do what Netflix does but then what the hell, lets use the correct unicode. |
Well, Netflix show u2026 correctly as a horisontal ellipsis on both my ipad and pc. Anyways, I think you did right. |
"-" in movie description is displayed as "u2013" with the "0" for some reason is with a thinner typeface.
The text was updated successfully, but these errors were encountered: