Intellego: Difference between revisions

Intellego (view source)

Revision as of 13:38, 20 March 2014

1,303 bytes removed , 20 March 2014

Removed "Technical Details" and cut the info down to a concise paragraph at the top of the page in order to clearly describe the product we are aiming to produce.

Jbeatty

Account confirmers, canmove, Confirmed users

2,357

edits

@@ Line 1: / Line 1: @@
 Intellego is a machine translation project for the benefit of Mozilla and the Open Web.
+__NOTOC__
 == Project details ==
+Intellego is a machine translation (MT) platform that seeks to unify existing open MT projects by providing a single API for engine developers and a unified web service that hosts a number of different language pairs/engines/implementations in the back end. The Intellego platform will allow users to select from a number of open MT engines based on the most prominent MT methodologies in order to find the best target MT output for their on-the-fly translation.
+The Intellego MT group and project are based on the following set of values:
 ; Our Mission
 : To provide users with automated translation, from any language, to any language, in real time, on any software or device that is useful to them.
@@ Line 11: / Line 13: @@
 ; Our Motto
 : We Will Be Understood.
-=== Technical details ===
-; Intellego will be a machine translation platform consisting of various open source engines based on the most prominent approaches to MT (i.e., SMT, RBMT, EBMT, and hybrid).
-: Research has revealed that certain approaches produce better output for certain language pairs and content types. For example, Russian's grammar is incredibly complex. So much so, that SMT output for Russian is usually very flawed. The RBMT approach has demonstrably produced better output for language pairs that include Russian. In addition, RBMT is best suited for long sentences and structured content, like wikis, whereas SMT is best suited for short sentences and user generated content.
-; Intellego will aim to provide a single API for engine developers and a unified web service that hosts a number of different language pairs/engines/implementations in the back end.
-: This aims to increase accessibility to smaller, more efficient MT engines on the web. Kevin Scannell gave this example: "If you look at Apertium for example, there are some language pairs that are better performing than Google Translate, and many pairs that Google doesn't support at all.  But they don't have the infrastructure to keep a web service up and running (they've tried and it's been up and down)." This will help break up the proprietary nature of MT and allow for a greater presence of open MT on the web.
-: In addition, it will help to satisfy our aim to make the Intellego platform available through an open API and web services, as is stated on the wiki.
-; The GSoC terminology-based project will serve as a pre-processing utility in the Intellego MT process to provide accuracy in translation.
-: Research suggests that when a user evaluates MT output, they tend to be more accepting of MT error when it is grammar based, rather than terminology based.
 == Project meetings ==