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
Then I opened it with Google Spreadsheets, the file was duplicated and auto converted to Google Spreadsheet. After that I deleted the original .csv file.
Then I ran babelish csv2strings --filename="test_data_with_percent_space.csv" --fetch --verbose --ignore-lang-path --sheet=0 --langs=English:"en" babelish returns a HTTP 400 error from Google. See details here: netbe/Babelish#46 (comment)
But when I create a new blank Spreadsheet file and I manually add "English/GREETINGS" everything works fine and downloads the contents. So there is no obvious problem with the auth token.
The text was updated successfully, but these errors were encountered:
I'm not exactly sure what went wrong. But there was some issue with CSV export in google_drive 0.3.x. It may be solved by using google_drive 1.0.0 instead, though it's still pre version. You can install it by:
$ sudo gem install --pre google_drive
You need to write:
spreadsheet.worksheets[0].export_as_string
to export it as CSV. Note that google_drive 1.0.0 is not 100% compatible with 0.3.x, and you may need to modify other part of your code too.
See netbe/Babelish#46
Use Case
First uploaded https://raw.githubusercontent.com/netbe/Babelish/master/test/data/test_data_with_percent_space.csv to Google Drive (I have auto convert off).
Then I opened it with Google Spreadsheets, the file was duplicated and auto converted to Google Spreadsheet. After that I deleted the original .csv file.
Then I ran
babelish csv2strings --filename="test_data_with_percent_space.csv" --fetch --verbose --ignore-lang-path --sheet=0 --langs=English:"en"
babelish returns aHTTP 400
error from Google. See details here: netbe/Babelish#46 (comment)But when I create a new blank Spreadsheet file and I manually add "English/GREETINGS" everything works fine and downloads the contents. So there is no obvious problem with the auth token.
The text was updated successfully, but these errors were encountered: