-
Notifications
You must be signed in to change notification settings - Fork 4
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
Windows support #3
Comments
I'll help testing next week, I have windows at work. |
It seems to be related to the Unicode support on Windows. Actually |
It seems that windows is a mess and mostly unsupported, and we would need a workaround. E.g. using the emoji name between colons, or an empty string, when an emoji is outputted. Or we can just use ASCII replacements for some emojis at least. E.g. smileys, and the rest can be empty string. |
Yeah, sounds good. I'll have another look at windows this week and sort things out a little better. After a couple of weeks dealing with more serious packages I could probably afford to do this package a bit in my train work. |
I'll see if this update helps at all. |
Hmm, interesting. If this fixes the fonts, can we detect whether it is I am afraid that the encoding conversion code in R will still fail, at
|
No effect here; still just a mess. I wonder if @kevinushey knows if it's possible at all? Or are we at the mercy of what Windows is willing to render here? |
Unfortunately I don't know a great solution here, UTF-8 on Windows (and in R + RStudio) is kind of a mess. :/ Surprisingly, R complains if you try to actually construct a string literal using that representation: > "\xf0\u009f\u0091\u008d"
Error: mixing Unicode and octal/hex escapes in a string is not allowed Just in case that's relevant... |
I'm getting test failures on windows 7; emoji conversion is not working there.
Happens in both Rstudio and Rgui (under VMware as I don't have a native machine). Similar failure happened on winbuilder.
The text was updated successfully, but these errors were encountered: