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
Translation: Bing CLI: Yes Version: 1.6.3
It could have a delay for each request, if you have the option for the dev to put it would be great BingTimeout: 8e3 GoogleTimeout: 5e3 ...
o Translating. Please wait. 89 of 428 translated.Translation error: HTTPError: Response code 429 (Too Many Requests) at Request.<anonymous> (C:\Users\lw\AppData\Roaming\nvm\v18.14.1\node_modules\@parvineyvazov\json-translator\node_modules\bing-translate-api\node_modules\got\dist\source\as-promise\index.js:118:42) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) { code: 'ERR_NON_2XX_3XX_RESPONSE', timings: { start: 1678404337629, socket: 1678404337629, lookup: 1678404337629, connect: 1678404337647, secureConnect: 1678404337715, upload: 1678404337715, response: 1678404337878, end: 1678404337879, error: undefined, abort: undefined, phases: { wait: 0, dns: 0, tcp: 18, tls: 68, request: 0, firstByte: 163, download: 1, total: 250 } } }
The text was updated successfully, but these errors were encountered:
This could be addressed with Google Translate by using the batch translate endpoint
Sorry, something went wrong.
Hey @AidanWelch, thank you for your suggestion. 😊
I quickly scan your batch implementation to the Google Translate API package (https://github.com/AidanWelch/google-translate-api#batch-translate) and that looks promising and game-changing.
I will try it out asap. Thank you!
No branches or pull requests
Translation: Bing
CLI: Yes
Version: 1.6.3
It could have a delay for each request, if you have the option for the dev to put it would be great
BingTimeout: 8e3
GoogleTimeout: 5e3
...
The text was updated successfully, but these errors were encountered: