Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upEncoding problems: reading Hebrew characters with `read_sheet` #26
Comments
|
Exactly the same thing is happening to me, now with Spanish accents.
The first output is correct, but the second is not:
Great library, but useless until this basic thing gets fixed |
|
Someone submitted curly apostrophes in a form response to me, so I'm seeing similar issues. This is only bad on my Windows machine. It's fine on Rstudio Server on CentOS 7. Windows result:
CentOS 7 result:
|
|
This has to be fixed in gargle. I could replicate all of this on my Windows VM and the gargle fix resolves it for me. It would be great to hear confirmation from others here. Note that, until that version of gargle goes to CRAN, you'll need to install the dev version from GitHub: |
|
@jennybc Works like a charm in the gargle development version. Thanks! |
|
I've updated gargle to dev gargle_0.4.0.9002 but I'm still getting these encoding problems with googlesheets4. Pretty sure Google Sheets and RStudio are both operating with UTF-8 as default encoding so it's strange. |
|
@adisarid would you mind sharing your code? I updated gargle (like @francisbarton did) but I keep getting the same encoding problems
I'm also posting my sessionInfo() in case it's useful
|
|
@silviaegt Did you restart R? Above, I am seeing the released version of gargle, not dev. |
|
Yaaay, that was what was missing, also I guess I wasn't suppose to "library(gargle)". Thank you so much @jennybc! |
|
Great! Yes, it is also true that you do not need to |
read_sheetfails when trying to read a google sheet with non standard characters (e.g., Hebrew text).I'm comparing it to
read_csvon a "web published" version of the same sheet, which behaves nicely.The googlesheet4 version:
comes up with this gibberish
were the web published csv version is read like this:
and provides the right version:
Any suggestions about how to fix this?