Since Japanese is so badly broken now, I’ve decided to help by making a series, starting off with examples of the worst of it. The translations that are WILDLY off. This has been reported before, but after several weeks it has not shown no improvement. Hopefully these real world examples will help.
I’ve got pictures of Lingq’s translations on my iPad, along with what Google Translate gave me for an actual real, working translation.
ALL of these happened within the past couple days of reading. Imagine trying to read a foreign language like this.
In recent days, the errors in Japanese-English automatic translation have been continuous and frustrating. I don’t know if it’s because the novel I’m currently reading contains a lot of dialogue, but I can’t count how many times Lingq has translated a Japanese sentence as “The most important thing is…” which obviously had nothing to do with the original text.
FWIW i imported 25 short books over the past year with zero issues. The last two have had constant issues including the issue I’ve showed in this post.
I really have two main issues and they are both translation related. The one I explained in this post, and the other one is that about one out of a dozen times the translation doesn’t load at all. Between these two translation bugs, reading is really painful. I’m lucky if I get half of my translations working. I’m barely getting by because after 25 short books I’ve gotten somewhat competent at reading, but that only lessens the pain a little, especially because it drains the fun out of the process.
Also, I have had long term language learning goals which keep me on it for hours per day, so it’s incredibly frustrating constantly running into these bugs. I’m not exaggerating either. What I pasted above was a tiny portion of what I ran into over those few days. I usually can’t go 5 sentences without a bad translation or one not loading.
I love this app, and I want to keep using it, and I’ve recommended it on language learning servers I’m on, despite it being pretty expensive. I’m really holding onto hope this will get fixed up like other things that have come and going over the past year.
@nsprung@zoran Since I discovered that the translation on the sentence editing screen is different, I’ve been conducting tests, and it’s clearly much better translated and also consistently translates the entire text (translations in sentence mode sometimes skip parts of the sentences). Not only does it translate well when there are Japanese brackets (「」), but the translations are much more accurate to the real meaning of the sentence.
@justfrozen I have also tested it in cases where the translation on the sentence view doesn’t load at all. While waiting the response, if you access sentence editing on iOS (as I explained in my previous post) and click the blue translation button, the translation loads immediately, and it’s probably even better than it would have been if it had worked correctly.
@roosterburton Have you noticed that there are two endpoints in LingQ that generate translations in iOS, and one of them (the one with the blue icon) is much better than the other? Which one do you use in your extension? What parameters do they require, are they equivalent?
@roosterburton The blue icon is in a different location within the application (in the phrase editing section); you have some screenshots in my previous messages. The endpoint has to be different because the translation result has nothing to do with the usual translation it performs (it’s way better).