Other Translation Engines

[looki]

It would be interesting to have some other translation engines implemented on Transposh. It will give more one option for translation engine if one or other of the current implemented translation engines get offline.
It will have some other purposes, for example:

• More different language pairs for translation;
• If one word dont get translated in on translation engine, there is the possibility to use another engine, and it will give a good result on the end text.

Here is a list of some translation engines and their links:

-Reverso  http://www.reverso.net/
-Free Translation and Professional Translation Services from SDL International  http://www.freetranslation.com/
-ToggleText?  http://www.toggletext.com/
-WorldLingo?  http://www.worldlingo.com/products_services/worldlingo_translator.html
-ForeignWord?  http://www.foreignword.com/Tools/transnow.htm
-Translated  http://free.translated.net/
-Pars Translator[scientific and technical field]  http://www.parstranslator.net/eng/translate.htm
-IMTranslator  http://free-translation.imtranslator.com/
-Lionbridge iTranslator  http://itranslator.lionbridge.com/bgsx/BGSXeng_us-EntryPage.htm
-LinguaWeb?  http://www.linguamatix.com/linguaweb/
-PSMT  http://psmt.sourceforge.net/
-ReTranslator?  http://prague.tv/toys/retrans/ Babelfish
-Comprendium[social and technical fields]  http://www.translendium.net:8080/home/index.jsp?locale=en
-Transparent  http://www.transparent.com/
-Applied Language  http://www.appliedlanguage.com/

[ofer]

Although I agree this ticket is basically valid, I would like you to edit the list according to a few criterias.

• They should have an api which one can use.
• They should not be duplicate (imtranslator is a google clone afaisi)
• They should respond in real time

After editing this list, I'll review and see what can be done

[looki]

Ok,

But it is missing in this list 2 other engines:

• Ask.com
• Yahoo Babelfish

[ofer]

This will be set to the feature complete version, I will have to check which ones are usable and to what extent, apertium shows promise:  http://api.apertium.org

[looki]

Hi,

Thanks for the updates, but, the main reasons I asked for all those engines to be implemented is to take advantage of somethings like:

• If one word or phrase dont get translated when using one engine, you can use another engine, so, to check if translations gone OK, you have to translate the same segment at least in 2 engines at the same time. I say it because I have many experiences with Google translating a phrase, but it is not really translated, and it dont give any error message, so I believe that in the Google Database, they dont have the right translation for the phrase. So, to get proper/reliable results, I think is a good idea to translate the same phrase in 2 different engines, and compare it.
• If one engine get down, you will have another translation engine for backup.
• The use of many engines will avoid banishment when you need to do mass translations at the same time or at least fast, and for my knowledge, today all online services are practicing bans constantly, to avoid resources abuse. By the way, in another point of view, when you are working with a site of news [articles, texts, etc], or something like this that have a great amount of data, you need to translate more at the same time, so you need a mass translation tool, and is required or desired to be done in the minor time as possible.

I have many more points of view that proof that is a good idea to implement all engines possible, but I think the 3 points I give in above paragraph is good enough.

In the other way, it will take an undesirable amount of time to get all this work done, I hope someone can help you, or you can find if some one already implemented a script for one of all the presented engines, to be easy to you find the way to use their API.

[ofer]

Added Apertium support in [571]