Closed zonuexe closed 2 years ago
Maybe google-translate-tk.el
can be removed.
I was checking the API with the intention of submitting the following patch, but in the process I found that it was okay to encode tk
with the wrong b-d1
parameter.
@atykhonov @stardiviner Hi, can you please review this PR in your spare time? This PR resolves #52. Simply remove the code for token generation that is no longer needed.
@zonuexe Does it work on your machine by appling this patch? We might need more test to confirm. I currently don't have Emacs on my hand. Can't verify this.
@stardiviner Yes, compilation and execution are successful in my environment.
Ok, I will test this PR in later. Thanks for confirming.
@stardiviner I missed some mistakes and pushed a commit to fix them.
And I rebuilt the CI for this project in another PR with GitHub Actions instead of the terminated TravisCI. https://github.com/atykhonov/google-translate/pull/151
@stardiviner I missed some mistakes and pushed a commit to fix them.
And I rebuilt the CI for this project in another PR with GitHub Actions instead of the terminated TravisCI. #151
Thanks for upating. I pulled your branch update and try to test. But my china network blocked translate.google.com. Can't access the service now. I need to find a way to fix this problem.
Finally got time to testing this network issue, confirmed this patch works. And this PR seems already merged. Done.
Perhaps Google Translation API is no longer validating the
tk
parameter.https://github.com/atykhonov/google-translate/issues/52 suggests that
google-translate--search-tkk
function returns a hard-coded pair of b-d1, but at least today It seems to work with any value.