R: How to handle raw/byte characters mixed with latin-1 characters
up vote
1
down vote
favorite
I have some e-mails that have raw instead of latin-1 characters for æ,Æ,ø,Ø,å,Å.
# My string
my_string = "Den vedh=E6ftede"
# Should be
"Den vedhæftede fil"
# Raw character for E6
> charToRaw("æ")
[1] e6
Is there any way to convert the data back to the correct format other than to do a string replace?
# Naive solution (with potential problems)
> gsub("=E6", "æ", "Den vedh=E6ftede")
[1] "Den vedhæftede"
String replace has the problem if "=E6" exists naturally in the e-mails.
Any suggestions?
r encoding utf-8 byte
add a comment |
up vote
1
down vote
favorite
I have some e-mails that have raw instead of latin-1 characters for æ,Æ,ø,Ø,å,Å.
# My string
my_string = "Den vedh=E6ftede"
# Should be
"Den vedhæftede fil"
# Raw character for E6
> charToRaw("æ")
[1] e6
Is there any way to convert the data back to the correct format other than to do a string replace?
# Naive solution (with potential problems)
> gsub("=E6", "æ", "Den vedh=E6ftede")
[1] "Den vedhæftede"
String replace has the problem if "=E6" exists naturally in the e-mails.
Any suggestions?
r encoding utf-8 byte
FWIW, that symbol has ane6
raw representation if the encoding islatin1
. InUTF-8
its byte representation isc3 a6
(2 bytes).
– nicola
Nov 8 at 14:15
This looks like Microsoft's mangling behaviour. I'm pretty sure it escapes naturally occurring strings that would otherwise be transcoded to hex.
– hrbrmstr
Nov 8 at 14:20
I just edited the "UTF-8" to the correct "latin1"
– Esben Eickhardt
Nov 8 at 14:53
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have some e-mails that have raw instead of latin-1 characters for æ,Æ,ø,Ø,å,Å.
# My string
my_string = "Den vedh=E6ftede"
# Should be
"Den vedhæftede fil"
# Raw character for E6
> charToRaw("æ")
[1] e6
Is there any way to convert the data back to the correct format other than to do a string replace?
# Naive solution (with potential problems)
> gsub("=E6", "æ", "Den vedh=E6ftede")
[1] "Den vedhæftede"
String replace has the problem if "=E6" exists naturally in the e-mails.
Any suggestions?
r encoding utf-8 byte
I have some e-mails that have raw instead of latin-1 characters for æ,Æ,ø,Ø,å,Å.
# My string
my_string = "Den vedh=E6ftede"
# Should be
"Den vedhæftede fil"
# Raw character for E6
> charToRaw("æ")
[1] e6
Is there any way to convert the data back to the correct format other than to do a string replace?
# Naive solution (with potential problems)
> gsub("=E6", "æ", "Den vedh=E6ftede")
[1] "Den vedhæftede"
String replace has the problem if "=E6" exists naturally in the e-mails.
Any suggestions?
r encoding utf-8 byte
r encoding utf-8 byte
edited Nov 8 at 14:28
asked Nov 8 at 14:09
Esben Eickhardt
507415
507415
FWIW, that symbol has ane6
raw representation if the encoding islatin1
. InUTF-8
its byte representation isc3 a6
(2 bytes).
– nicola
Nov 8 at 14:15
This looks like Microsoft's mangling behaviour. I'm pretty sure it escapes naturally occurring strings that would otherwise be transcoded to hex.
– hrbrmstr
Nov 8 at 14:20
I just edited the "UTF-8" to the correct "latin1"
– Esben Eickhardt
Nov 8 at 14:53
add a comment |
FWIW, that symbol has ane6
raw representation if the encoding islatin1
. InUTF-8
its byte representation isc3 a6
(2 bytes).
– nicola
Nov 8 at 14:15
This looks like Microsoft's mangling behaviour. I'm pretty sure it escapes naturally occurring strings that would otherwise be transcoded to hex.
– hrbrmstr
Nov 8 at 14:20
I just edited the "UTF-8" to the correct "latin1"
– Esben Eickhardt
Nov 8 at 14:53
FWIW, that symbol has an
e6
raw representation if the encoding is latin1
. In UTF-8
its byte representation is c3 a6
(2 bytes).– nicola
Nov 8 at 14:15
FWIW, that symbol has an
e6
raw representation if the encoding is latin1
. In UTF-8
its byte representation is c3 a6
(2 bytes).– nicola
Nov 8 at 14:15
This looks like Microsoft's mangling behaviour. I'm pretty sure it escapes naturally occurring strings that would otherwise be transcoded to hex.
– hrbrmstr
Nov 8 at 14:20
This looks like Microsoft's mangling behaviour. I'm pretty sure it escapes naturally occurring strings that would otherwise be transcoded to hex.
– hrbrmstr
Nov 8 at 14:20
I just edited the "UTF-8" to the correct "latin1"
– Esben Eickhardt
Nov 8 at 14:53
I just edited the "UTF-8" to the correct "latin1"
– Esben Eickhardt
Nov 8 at 14:53
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53209457%2fr-how-to-handle-raw-byte-characters-mixed-with-latin-1-characters%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
FWIW, that symbol has an
e6
raw representation if the encoding islatin1
. InUTF-8
its byte representation isc3 a6
(2 bytes).– nicola
Nov 8 at 14:15
This looks like Microsoft's mangling behaviour. I'm pretty sure it escapes naturally occurring strings that would otherwise be transcoded to hex.
– hrbrmstr
Nov 8 at 14:20
I just edited the "UTF-8" to the correct "latin1"
– Esben Eickhardt
Nov 8 at 14:53