Displaying 3 results from an estimated 3 matches for "enc2".
Did you mean:
ec2
2017 Aug 01
3
special latin1 do not print as glyphs in current devel on windows
...ot;0002", etc. see
http://www.cp1252.com/.
The exception is the cp1252 "80" to "9F" code range. E.g. the Euro sign is
"80" in cp1252 but "20AC" in Unicode, endash "96" in cp1252, "2013" in
Unicode.
The same error seems to happen with
enc2utf8(x)
Now with iconv() the result is as expected.
iconv(x, to = "UTF-8")
The second problem IMO is that encoding markers get lost with the enc2*
functions
x_utf8 <- enc2utf8(x)
Encoding(x_utf8)
x_nat <- enc2native(x_utf8)
Encoding(x_nat)
Again, this is not the case with iconv...
2017 Aug 01
0
special latin1 do not print as glyphs in current devel on windows
.../www.cp1252.com/.
> The exception is the cp1252 "80" to "9F" code range. E.g. the Euro sign is
> "80" in cp1252 but "20AC" in Unicode, endash "96" in cp1252, "2013" in
> Unicode.
> The same error seems to happen with
>
> enc2utf8(x)
>
> Now with iconv() the result is as expected.
>
> iconv(x, to = "UTF-8")
>
>
> The second problem IMO is that encoding markers get lost with the enc2*
> functions
As you are changing encodings, you do not want to preserve encoding!
> x_utf8 <-...
2017 Aug 01
2
special latin1 do not print as glyphs in current devel on windows
...interested in preserving encodings. What I am worried about is
that the encoding is not marked anymore, i.e. that Encoding() returns
"unknown".
In cp1252 encoding on Windows (note that I am using the cp1252 escape
"\x80" and not the Unicode "\u20AC")
> x_utf8 <- enc2utf8(c("?", "\x80"))
> Encoding(x_utf8)
[1] "UTF-8" "UTF-8"
> x_nat <- enc2native(x_utf8)
> Encoding(x_nat)
[1] "unknown" "unknown"
See also Kirill's message to this list: "ASCII strings are marked as ASCII
internally,...