In my experience Deepl is consistently, without fail, considerably better than Google Translate. I basically use Google now only for more exotic language pairs, or full-page translations.
And recently everything I had to look up while reading Gabriel García Márquez, DeepL didn't know. After enough failures I gave up and returned to Google Translate for the remainder of the book.
Moreover, Google often provides a single target word; whereas DeepL allows you to select from a range of synonyms clicking on a word, and will adjust the sentence accordingly to use the new word. When Google gets the context wrong and provides the wrong meaning for the translation, DeepL's capability to translate with a different meaning is invaluable.
I've found that sometimes what Google does for these is translate from Language A > English, and then English > Language B, which leads to bizarre results.
So yes, there's an intermediary language. But it's not English.
https://www.newscientist.com/article/2114748-google-translat...
For example, translating "рубанок" ("plane", in the sense of the carpenter's tool) from Russian to Polish used to produce "samolot" ("airplane") in Google translate up until sometime earlier this year, because in the intermediate representation "plane" was ambiguous just like it is in English. It looks like that particular bit is fixed now, which is at least progress! Maybe they've been adding more non-English text pairs...
And I gave the Hindi input in devanagari (राम आ गया), but still the Nepali translation ended up being the equivalent of 'the sheep came' (भेडा आयो), so somewhere along the line it seemed to be treating the name राम (rām) as equivalent to the English string 'ram' and translating accordingly.
So if the intermediate language isn't English, it certainly has some English-like properties....
Considering Translate is such an important product, I can't fathom why they just don't hire a single linguist (or just anyone who isn't completely clueless, really) per language to register decent translations, or at least import them from a real dictionary...
How many people on Google Translate actually are able to reasonably verify translations? Relatively few - and those qualified few who might poke at Translate out of curiosity are just as likely not to feel inclined to offer free labour to Google.
> Considering Translate is such an important product, I can't fathom why they just don't hire a single linguist (or just anyone who isn't completely clueless, really) per language to register decent translations, or at least import them from a real dictionary...
Perhaps professional translators rather than linguists. I imagine they have some linguists on the project, but they're likely to be more NLP-type linguists.
The difficulty is that they're interested not just in word-level meaning/translation-accuracy, but also phrase- and clause-level accuracy, and those are really large (i.e. theoretically infinite) spaces.
I've heard that the Spanish<->English translations aren't too bad.
One example is technical/service documentation for a heavy machinery company I worked for. The tech writers were based in Germany, but O&M Manuals were required in Japanese for sale in Japan. Those docs were translated using English as a "pivot language". Usually dictated by pricing (fewer German+Japanese translators = much higher cost).
And in any case, for German->Japanese, going through English probably has a lower cost. But for Hindi->Nepali, you'll lose a lot of information as Hindi and Nepali are closely related and similar not only in terms of correspondences between vocabulary items, but also grammatical structures, which is effectively 'thrown away' if there's an English, or close-enough-to-English-to-effectively-be-English intermediate translation language. (Not to mention the inefficiencies of the equivalent of sending a package from Delhi to Kathmandu via London.....)
For example it will always translate 'order' in a sentence as 'Befehl' (I order you to fix a steak) instead of 'Bestellung' (I order a steak).
Both are correct, but completely different, and in our context we never mean the former.
The Teacher said that it was amazing and that many native students she had couldn't write that well.
Google has clearly made it their mission to solve that problem, and I'd say they've been rather successful.
The bigger problem is likely to be lack of training data. Unless they have a pile of cash to pay professional translators to produce a parallel corpus, the alternative is to scrape translations from the internet. Basically, crawl the same site multiple times with different Accept-Language headers and try to align the results. Crucially, this depends on an existing ecosystem of bilingual websites with high-quality human translations.
According to DeepL's website they're a spin-off of Linguee, who provide a search service for exactly that kind of parallel data. So before DeepL starts supporting any given language pair, you should expect it to appear in Linguee first. https://en.wikipedia.org/wiki/Linguee
Edit: It took me a while to figure out how to select a different language on https://linguee.com (Their UI seems broken using mobile Firefox Preview.) Appending /english-chinese and /english-japanese to the URL shows that they already support those two, and the alignment of translations appears reasonable to me. No /english-arabic, though.
only has 9 language options(8 if you exclude the dest language).
But once you step away from it, quality goes down. I tried translating random pieces of Russian literature and it makes obvious mistakes. It can't even manage the structure of sentences, never mind word choice.
Translations from English are also bad. For example, it translated "I never felt that the translation is off" as "I never felt that the translation is turned off".