-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
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
Failed to search TKK #52
Comments
Hi @renatofdds, which version do you use? |
I'm also having this problem. Using most recent version 0.11.11 |
I'm also on 0.11.11 |
Facing the same issue on 0.11.11. Any help is highly appreciated, |
Hi all! I have no idea what exactly could be the root cause of the issue. But with your help I believe the reason could be discovered and the issue fixed. I've just pushed the code ( With these changes, please, execute |
If you'll see that someone already posted the similar output as you get, please feel free to post it again, or just notify that you get the same output. I just believe that additional information would be helpful. Actually any help is highly appreciated! Thank you in advance! |
Thank you for the efforts and further steps. I will report the test results soon. |
After upgrading to 0.11.12 and setting the debug to true as you suggested I did a google-translate-smooth-translate. I don't see two windows open and I receive the same error. This is what happens Translate : "The text to be translated appears here correctly (Japanese)" RET But version 0.11.10 works perfectly at my home computer (11.11 and 11.12 not tested yet). The above test was from my office computer and the only difference is that, the office computer is behind a http proxy. So I strongly doubt it has something to do with proxy. Further testing for connection through proxy
Since google translate has to establish a connection to https://translate.google.com, i strongly suspect it has something to do with my proxy setting. Sorry if I wasted your time. But I would sincerely appreciate if you can point out some ways I can make it to work in my work-computer behind proxy. I also hope many people need google translate in their office computer which is normally behind a proxy. Thank you for your time and efforts |
Interesting. My case is opposite. While it works on my office computer, doesn't work on my home computer. Both uses same emacs settings including google-translate's versions(0.11.13). EDITED:
|
SOLVED Either modify that one particular .el file and rebuild you emacs OR update to 'emacs-snapshot' version-26. I took the easier step and updated to Emacs-26.0.50.2. Now google-translate works like a charm within emacs. |
@jack836 Good news. Thank you for sharing. |
When I updated Emacs 25.1 to Emacs 25.2, I found the issue. The issue is solved on my PC when (when (and (= emacs-major-version 25) (<= emacs-minor-version 2))
(setq google-translate-base-url
"https://translate.google.com/translate_a/single"
google-translate--tkk-url
"https://translate.google.com/")) I am uncertain about the issue at Emacs 25.1 Wish it will be helpful. Info:
|
I met the same problem. After configuring a socks5 proxy for emacs, the problem got addressed. Maybe it's concerning to the ISP, who blocks the network traffic to google services. However, I found something weired. With network proxy set globally in gnome 3, the google services can be visited by firefox browser, but they are not available in eww web browser in emacs. The socks5 proxy settings in gnome 3 seems to be ignored. example socks5 proxy for emacs:
|
This just started happening to me after months without a problem. But, it went away after a few minutes. I am not using a proxy. UPDATE: Now using a different computer that also worked without a problem. It's now failing with the same message. |
Same problem here. It has been working for months without a problem, but now i get |
same issue here /'' ( |
same here
|
The problem seems to be that the google-translate/google-translate-tk.el Line 50 in d8b84a8
does not match the appropriate string in the retrieved HTML document, which in my case was
I'm also running Emacs 26.1 and version 0.11.14. |
same here, I'm investigating and looking for a solution |
yes, previously HTML had something like the following:
now we have this representation: |
I found a quick fix. Try it:
You can use |
Emacs 25.1.1; A stubborn error in the Messages buffer:
even if I change:
|
Same here. |
I had the same problems two days ago. @SunDawning (use-package google-translate
:ensure t
:config
(when (and (string-match "0.11.14"
(google-translate-version))
(>= (time-to-seconds)
(time-to-seconds
(encode-time 0 0 0 23 9 2018))))
(defun google-translate--get-b-d1 ()
;; TKK='427110.1469889687'
(list 427110 1469889687)))) |
@edurante Thanks for your workaround! I also use -:config
+:init |
I'm very sorry! The above patch in #52 (comment) is my misunderstanding. 🙇 Also, I need this workaround using (use-package google-translate
:config
;; ...
;; Workaround in https://github.com/atykhonov/google-translate/issues/52#issuecomment-424302439
;; ...
;; BEGIN: Workaround which I need
(bind-keys*
("C-c t" . google-translate-at-point)
("C-c T" . google-translate-at-point-reverse))
;; :bind (("C-c t" . google-translate-at-point)
;; ("C-c T" . google-translate-at-point-reverse))
;; END
) |
@SunDawning it works very well! Thanks a lot! I'm preparing a patch based on the workaround. |
@dvzubarev it works out of the box for me (without any issue). |
I supposed this is kind of an issue that we experienced before when for part of the users In the meantime, I've just merged #91 that provides several backends ( |
* Set the new variable `google-translate-backend-method`. * Remove unnecessary workaround. See also: * atykhonov/google-translate#52 (comment) * atykhonov/google-translate#91
Hola a todos, hablare en español porque mi ingles es increíblemente pésimo y tal ves se me entienda menos de ese modo. tuve exactamente el mismo problema de ustedes pero con el Textractor, y llame a la compañía de internet para intentar cambiar mi ip, ya que no se cambiaba de manera tradicional a pesar de supuestamente ser una ip dinámica, y al ayudarme la chica del call center me dijo que había un bloqueo en mi router, que me lo quito, pero que evite usar ese tipo de programas porque ellos no ofrecen ese tipo de servicio, no entendi muy bien a lo que se refería, ya que se muy poco de programación, pero aun asi me quedo claro que el problema era un bloqueo en el router. no se si esto es lo que genera todo, o solo es mi caso particular en todo casi si a alguien le sucede este problema especialmente con el uso de textractor, y tiene servicio con claro, llamen a servicio al cliente, puede ser el mismo bloqueo que yo tenia. |
I tried with 0.11.18, but it works neither with curl nor the emacs backend:
|
This works for me with google-translate-backend-method set to 'curl. You also need to use require google-translate (if you are using use-package) before redefining the function. Hence my setup is (require 'google-translate) |
This reply fixed it for me :
|
This should be useful to help implement a true fixed version: https://github.com/Boudewijn26/gTTS-token/blob/master/docs/november-2020-translate-changes.md |
Fixed error: google-translate--search-tkk: Search failed: ",tkk:'" atykhonov/google-translate#52 (comment)
Fixed error: google-translate--search-tkk: Search failed: ",tkk:'" https://github.com/ atykhonov/google-translate/issues/52#issuecomment-727920888
(defun google-translate--search-tkk () "Search TKK." (list 430675 2721866130)) works for me. Thanks! |
this also work for my version: |
I wonder why the maintainers don't include the 2 lines into google-translate sources? |
This bug exists already since I started using Spacemacs about 1.5 year ago. Because it was already reported upstreaim in [this issue](atykhonov/google-translate#52), I implemented this fix only locally. However it becomes time now to implement this fix globally, to fix the google-translate functionality by default.
This bug exists already since I started using Spacemacs about 1.5 year ago. Because it was already reported upstreaim in [this issue](atykhonov/google-translate#52), I implemented this fix only locally. However it becomes time now to implement this fix globally, to fix the google-translate functionality by default.
For me too. |
Any translation attempt is failing with the error:
google-translate--search-tkk: Failed to search TKK
The text was updated successfully, but these errors were encountered: