Nearly every blue word I mouse over is now defined as “google translate”. What’s going on - did something change? Mac, chrome, desktop. My connection is extremely fast.
Hi Wulfgar,
Are you saying that you can’t see user hints? If there are not user hints created for that word, only Google Translate suggestion will appear. For which study/dictionary language you have a problem?
I’m saying the words “Google Translate” rather than the actual translation appear for most, but not all blue words. In the past this only happened when the connection was bad, but no matter how long I wait the definition doesn’t appear.
I’m using Korean. I just checked, and the word 그래도저는 does this. I’m using default settings regarding dictionaries.
With my intermediate stuff, this isn’t a big deal, because hints have been created for most words. But when I read an actual news article, there are about 60 unknown words per minute of audio now, and most have no user hints created.
I have a similar problem with Russian actually
1 Like
Me too with Spanish. However, sometimes the actually translation (From Google) would appear like it’s supposed to. The majority of the time, no.
1 Like
The google translate doesn’t seem to be working. Most words in all my languages are now saying “no hints available”. Even for words that are coming up fine on google.com translate
1 Like
Hi Wulfgar,
We are looking into the issue, thanks for letting us know. What is your dictionary language? if you check on the Google Translate, is the translation available for words with which you are having this issue?
We are looking into the issue. Thanks for your patience!
1 Like
Korean. Yes, translation is available for all words if I use google translate directly.
I confirm: automatic translations don’t seem to be working, or only sporadically. For the last three days or so at least.
I’m hoping this is your highest priority right now. It’s pointless for me to use lingq to read difficult material now, since it almost never supplies translations.
The fix will be on production soon. Thanks for your patience!
1 Like
The issue should be fixed now. Can you please check and let us know if it works properly for you? Thanks for your patience everyone!
It appears to be working now. Thanks!
1 Like
Ok, there’s another problem, and this one has been around for much longer. When you take the google translation, you aren’t taking the main translation.
If I put 돌아다녀서 in google translate manually, “Go around” pops up. If I click on the translation, google usually gives me a list of optional phrases. In this case there is only one optional phrase, and it is “Dolahdanyeoseo”. Your program is using Dolahdanyeoseo. I haven’t verified, but I think your program always takes the bottom phrase, which is usually the worst option. Can you please make it take the first choice?
1 Like
Thanks for letting us know Wulfgar. We’ll check that.
Any progress on this? Not as bad as the original problem on this thread, but still sucks up a lot of my time.
It’s reported to our developers and I’ll let you know as soon as I hear back from them.
Hi Wulfgar,
Just to let you know that we figured out that the issue you reported was related to specific languages only (including Korean as you said). It has been fixed now and from now on Google Translate will show best suggestion for highlighted phrases. Thanks for letting us know!
1 Like
I did a quick check and it looks good. Thanks!