Account confirmers, canmove, Confirmed users
2,357
edits
Intellego: Difference between revisions
Jump to navigation
Jump to search
→Project details: Enhanced details for project details
(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.) |
(→Project details: Enhanced details for project details) |
||
| Line 3: | Line 3: | ||
== Project details == | == 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. | 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. | ||
;Breaking closed ecosystems | |||
The current machine translation ecosystem is dominated by proprietary, closed systems. This includes their code base, their data collection processes, and public accessibility to their language resources. Additionally, the open MT ecosystem suffers from being unable to reach the vast majority of participants on the web through web services or APIs. | |||
MT users are limited to using engines that follow a single MT methodology for all language pairs and content types. Studies have shown that a one-size-fits-all approach in MT does not provide the user with optimal translation output. Users need a single access point to different MT engines following different MT methodologies that will produce the best quality output by selecting the right engine for the right language pair. An open MT ecosystem is the best way to accomplish this. | |||
; | ;Machine translation in Firefox | ||
Google's ability to provide users with automatic translation of web content using Google Translate attracts global users to the Chrome browser. Intellego aims to be to Firefox what Google Translate is to Chrome by powering the automatic translation feature within the browser. | |||
; | ;Machine translation at Mozilla | ||
Many Mozilla l10n teams consist of only 1-2 people. While they would love to be able to provide l10n coverage for all of the Mozilla support sites (and other projects) they do not have the time or resources to accomplish the task. Users, thus, have a localized Firefox, but lack documented product support in their language. | |||
Additionally, Mozilla's unique, linguistically diverse community frequently encounters language barriers to participation. Accessibiity to a Mozilla operated MT project can lower the language barrier and create a more inclusive experience for the next million mozillians. | |||
;Advancements in MT research | |||
: | Language support selection for machine translation projects are driven, in part, by ROI and availability of resources. This often results in minority languages, and even some majority languages (see Indic languages) being under-represented in the machine translation ecosystem. While ROI continues to be a primary motivator for incorporating support for these languages, they will remain under-represented and unsupported. | ||
Explore the wiki for more details about the [https://wiki.mozilla.org/Intellego/Mission Intellego project's purpose and focus.] | |||
== Project meetings == | == Project meetings == | ||