You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After decoding the message payload, gmailr could extract the charset from the Content-Type header. By default on the web, this is iso-8859-1, which R calls "latin1". That could be set on the string, e.g.,
Encoding(x) <- "latin1"
But then again, I'm not sure where that actually helps, since R always displays and writes strings in the current locale, so things get weird.
The text was updated successfully, but these errors were encountered:
I am definitely not an expert on how character encodings work in R. However setting the encoding based on Content-Type seems to me like something httr should handle if it provides a benefit...
After decoding the message payload, gmailr could extract the
charset
from theContent-Type
header. By default on the web, this is iso-8859-1, which R calls "latin1". That could be set on the string, e.g.,But then again, I'm not sure where that actually helps, since R always displays and writes strings in the current locale, so things get weird.
The text was updated successfully, but these errors were encountered: