Translation not working - always returns empty string as response #115
Comments
@jschnurr Hi. I see you did the change to the json format. May I ask, where/how did you find out about the |
I don't recall. I do know that the documentation was limited / non-existent. |
Google did indeed change the format. The request still works, but the response body is no longer a |
They also added a new code parameter to validate requests from their apps exclusively. |
I provided PR #118 last night, but it doesn't deal with this extra parameter. |
Yeah. We've been working in the same :( |
The solutions are similar. It seems there are two factors that can cause "empty string" and/or 403 results from the Google Translate API:
headers = {'Connection': 'keep-alive',
'Accept': '*/*',
'User-Agent': ('Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) '
'AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18'
'.0.1025.168 Safari/535.19')
Perhaps we should go with a 'belt and suspenders' approach here, and merge them together. What do you think? |
It can't hurt I suppose. And I see in the inspector that Google is using them so why not. |
Hello,
Google must have changed something.
I will post an update if I find out something...
The text was updated successfully, but these errors were encountered: