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
This Twitter conversation reminded me of past pain I've had importing from Excel with unknown encoding. Maybe we could offer a little function that just exposes encoding info, even if someone goes on to import with a more conventional package. Reinforces the idea that one productive role for rexcel is for Excel diagnostics and troubleshooting xlsx import.
I note that when I migrated Gapminder data extraction from gdata to readxl, I was able to drop the explicit encoding specification. So some packages, presumably readxl among them, do figure this out for themselves, quietly.
The text was updated successfully, but these errors were encountered:
readxl and googlesheets issues seem to have a steady trickle of spreadsheets from Russia 😬. Gapminder also has some non UTF-8 sheets. Maybe we should systematically download those and make the "Gapminder corpus"?
This Twitter conversation reminded me of past pain I've had importing from Excel with unknown encoding. Maybe we could offer a little function that just exposes encoding info, even if someone goes on to import with a more conventional package. Reinforces the idea that one productive role for
rexcel
is for Excel diagnostics and troubleshooting xlsx import.I note that when I migrated Gapminder data extraction from
gdata
toreadxl
, I was able to drop the explicit encoding specification. So some packages, presumablyreadxl
among them, do figure this out for themselves, quietly.The text was updated successfully, but these errors were encountered: