We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
最近谷歌翻译和谷歌API都突然不能用了,之前一直都可以,用着梯子和全局,访问外网正常。
[请求错误]
此翻译引擎不可用,可能是密钥错误,也可能是请求过快。 可以尝试其他翻译引擎,或者来此查看相关回答: https://zotero.yuque.com/staff-gkhviy/pdf-trans/age09f
请注意,这些错误与 Zotero 和本翻译插件无关,由该翻译服务引起: Google(API)
Error: HTTP GET https://translate.googleapis.com/translate_a/single?client=gtx&sl=en-US&tl=zh-CN&hl=zh-CN&dt=at&dt=bd&dt=ex&dt=ld&dt=md&dt=qca&dt=rw&dt=rm&dt=ss&dt=t&source=bh&ssel=0&tsel=0&kc=1&tk=964953.560429&q=Assume%20L%20rounds%20of%20message%20exchanges%2C%20and%20take%20the%20lth%20round%20for%20example%3A%20the%20source%20n failed with status code 429
No response
The text was updated successfully, but these errors were encountered:
https://stackoverflow.com/questions/66370556/429-errors-returned-from-google-translate-when-using-googletrans-library
Sorry, something went wrong.
windingwind
No branches or pull requests
Is there an existing issue for this?
Have you checked the FAQ (#6)?
Are you using the latest Zotero and the latest plugin?
Environment
Describe the bug
最近谷歌翻译和谷歌API都突然不能用了,之前一直都可以,用着梯子和全局,访问外网正常。
Debug Output
[请求错误]
此翻译引擎不可用,可能是密钥错误,也可能是请求过快。
可以尝试其他翻译引擎,或者来此查看相关回答:
https://zotero.yuque.com/staff-gkhviy/pdf-trans/age09f
请注意,这些错误与 Zotero 和本翻译插件无关,由该翻译服务引起: Google(API)
Error: HTTP GET https://translate.googleapis.com/translate_a/single?client=gtx&sl=en-US&tl=zh-CN&hl=zh-CN&dt=at&dt=bd&dt=ex&dt=ld&dt=md&dt=qca&dt=rw&dt=rm&dt=ss&dt=t&source=bh&ssel=0&tsel=0&kc=1&tk=964953.560429&q=Assume%20L%20rounds%20of%20message%20exchanges%2C%20and%20take%20the%20lth%20round%20for%20example%3A%20the%20source%20n failed with status code 429
Anything else?
No response
The text was updated successfully, but these errors were encountered: