There's a good machine translation engine at http://translate.yandex.ru with quite permissive terms of use (free access, up to 10,000 request a day or 1,000,000 requested characters), and it has an API with HTTP access with XML-, JSON- (JSONP-) interfaces. At the moment it supports the following lang pairs:
en-ru
ru-en
ru-uk
uk-ru
pl-ru
ru-pl
tr-ru
ru-tr
de-ru
ru-de
Could it be possible to add a possibilty to use this as one of OT machine translation options?
More about Yandex translate API here: http://api.yandex.ru/translate/. It's in Russian, but their own translate engine does quite a good job translating it into English: http://translate.yandex.net/tr-url/en+ru.ru/api.yandex.ru/translate/
My impression is that this API cannot be used for commercial usage.
By navigating through the machine translation of terms and conditions, I see the following:
1.2. Your use of the Service is governed by these terms and Conditions, as well as:
...
Conditions of use of the service «Яндекс.Перевод», located at the address: http://legal.yandex.ru/translate_termsofuse/.
And, at the above address:
2.3. The service is available to the User for personal, non-commercial use.
Didier
That's right, commercial use isn't allowed.
On the other hand there are quite a few translators (particularly in Eastern Europe/ex-USSR) who work in the spheres of education, charity, civil/human rights, religion/faith etc. and whose translation work is not and cannot even be commercial.
I've written to Yandex Support concerning using their API for not strictly personal, but non-commercial use. I'll post their reply here as soon as they write back.
Ok, after half a year I recalled having received a positive answer from Yandex concerning their API in non-commercial and not strictly private use. They allow to use their service for non-commercial organizations (the e-mail conversation is attached here, originally in Russian, translated by Yandex MT into English).
While realizing the low priority of this Feature Request (limited number of langpairs, and, more importantly, quite limited legitimate use for the majority of OmegaT users), I presume that it wouldn't be too hard to implement. I have made a bash script to retrieve current segments translated by Yandex TM, but my Java knowledge is next to non-existing to deploy a TM plugin for OmegaT. I tried to play around with it using the ones already there in the tree as a guide, but to no practical avail (compiles fine, spits out just junk at best). It would be greatly appreciated if this TM could be used from within OmegaT.
Kos, https://sourceforge.net/p/yandextranslatepluginforomegat/wiki/Home/ - check this out (Yandex Transation Plugin for OmegaT).
Hi, thank you very much for looking into this. I'm currently not at home to check your implementation. I'll be able to check it on Tue, and I'll imediatelly write back to you.
oisee oisee@users.sf.net wrote:
Related
Feature Requests:
#790Ok, thank you for early response =)
Best regards, oisee.
The key -Dyandex.api.key=xxx must be supplied on the command line or in the usual launchers (OmegaT.l4J.ini, OmegaT.sh, OmegaT or omegat.kaptn).
Didier
Closed in the released version 3.1.9 of OmegaT.
Didier