Displaying 3 results from an estimated 3 matches for "x_un".
Did you mean:
d_un
2017 Sep 14
2
special latin1 do not print as glyphs in current devel on windows
......], taking any marked encoding into account."
Since the marked encoding is wrong, so is the output of enc2utf8().
> enc2utf8(x)
[1] "\u0080" "\u009e" "\u009a" "?"
Now, when we set the encoding to "unknown" everything works fine.
> x_un <- x
> Encoding(x_un) <- "unknown"
> print(x_un)
[1] "?" "?" "?" "?"
> (x_un2utf8 <- enc2utf8(x_un))
[1] "?" "?" "?" "?"
Long story short: The characters in the 80 to 9F range should not...
2017 Sep 14
0
special latin1 do not print as glyphs in current devel on windows
...t; account." Since the marked encoding is wrong, so is the output of
> enc2utf8().
>
> > enc2utf8(x)
> [1] "\u0080" "\u009e" "\u009a" "?"
>
> Now, when we set the encoding to "unknown" everything works fine.
>
> > x_un <- x
> > Encoding(x_un) <- "unknown"
> > print(x_un)
> [1] "?" "?" "?" "?"
> > (x_un2utf8 <- enc2utf8(x_un))
> [1] "?" "?" "?" "?"
>
> Long story short: The characters in...
2017 Aug 01
2
special latin1 do not print as glyphs in current devel on windows
Thank you!. My apologies again for not including the console output in my
message before. I sent another e-mail with the output in the meantime, so
it should be a bit clearer now, what I am seeing. In case I missed
something, please let me know.
Yes, I am using latin1 and cp1252 interchangebly here, mostly because
Encoding() is reporting the encoding as "latin1". You presumed correctly