Using the Machine Translation Portal

The Machine Translation Test Portal provided by Language I/O allows our users to compare translation quality across our many integrated machine translation engines. 

Login to the Portal

  • Navigate to     
  • Click on Machine Translation Portal
  • Login with the portal credentials provided by your Language I/O contact. 

Configure Your Translation Request

  • Once logged in, the portal home page will allow you to enter the content you wish to translate, along with the source locale, target locale and other options.


  • As shown in the screenshot above, enter the text you wish to translate in the area labeled Text to Translate.
  • Next to Source Locale, select the language of the entered text.
  • Next to Target Locale, select the language you wish to see your text translated into
  • Select Compare Translation Vendors if you wish to compare translations across all of the machine translation (MT) engines that your account is associated with. 
  • Note that the Debug option is only available to developer accounts. For developer access, select Debug to see additional output demonstrating which of your glossary terms were imposed upon each of the integrated MT engines.


Understanding Your Translation Results

  • For non-developer accounts and when the Debug option is not selected in developer accounts, you will see a single result per MT engine as shown below. If the term "glossary" is appended to the MT engine name, this means your glossary terms (or preferred translations for certain words and phrases that have been loaded into your Language I/O account configuration) were detected in your source content and were included in the translation. In the example below, the term "Language I/O" was the glossary term and the rule stipulated that it remain "Language I/O" in the target language as well - or remain untranslated. We can see that it was appropriately enforced across all of the MT engines.

[Note: to avoid any bias when evaluating quality, the names of the MT engines have been replaced with aliases.]



"Gulfstream" translation (glossary)


"Skytrain" translation (glossary)


  • When the debug option is selected for developer accounts, you will see several stages of translation for each integrated MT engine. 
  • The first stage labeled "pre-translation glossary" shows the source content with each glossary term that was detected delimited in some fashion. In the example below, you will see that the we detected the term "Language I/O" in the source content and wrapped it in tags. 
  • The second stage labeled "glossary pre-cleanup" shows the glossary term still wrapped in tags, but embedded in the translated content passed back by the MT engine. 
  • The third stage labeled "glossary" will show the complete translation, but with the tags removed. 
  • The fourth stage labeled "no glossary" (not shown below) will include the MT engine output without the glossary term imposed - or as the translation would look without Language I/O imposing any glossary terms.


"Gulfstream" pre-translation (glossary)


"Gulfstream" translation (glossary pre-cleanup)





Please sign in to leave a comment.
Powered by Zendesk