Scenarios for using MT and when to request human translation
Probably the most common question we get about using Globalization Pipeline is about machine translation quality. Is it any good? Well -- that depends on a number of factors -- the quality of the English source, the target language, and the domain of the content. IBM Globalization Pipeline offers development teams the ability to get raw machine translation of their application content, almost instantly, however whether the team chooses to deploy that content to customers is a different question.
Initially, when you are developing a new product, you probably want to use MT only in test and beta situations. Once your code (particularly user-visible content is stable), you would then submit your source for human translation through Globalization Pipeline. However, when your service is in production and changes and additions to the UI are quite small, you may want to simply deploy the MT of the new/changed content, and follow up quickly with human translation. These are risks the product team needs to assess. The decision is up to you!!
When and why you deploy machine translation and how often you choose to engage human translators is really up to you! Please be aware, that even though Globalization Pipeline makes it easy to send content for human translation whenever you wish (some teams have considered every time a string is changed or added), from a cost perspective, this approach could be cost prohibitive. Nonetheless, the beauty of Globalization Pipeline is it accommodates itself to the way in which you want to work.
What MT languages does Globalization Pipeline support?
Globalization Pipeline uses Straker MT API for machine translation. Machine translation for languages below from English and to English is currently supported:
- Arabic
- Basque
- Bengali
- Bosnian
- Bulgarian
- Catalan
- Chinese (Simplified)
- Chinese (Traditional)
- Croatian
- Czech
- Danish
- Dutch
- Estonian
- Finnish
- French
- French (Canada)
- German
- Greek
- Gujarati
- Hebrew
- Hindi
- Hungarian
- Indonesian
- Irish
- Italian
- Japanese
- Korean
- Latvian
- Lithuanian
- Malay
- Malayalam
- Maltese
- Nepali
- Norwegian (Bokmål)
- Polish
- Portuguese
- Romanian
- Russian
- Serbian
- Sinhala
- Slovak
- Slovenian
- Spanish
- Swedish
- Tamil
- Telgu
- Thai
- Turkish
- Ukrainian
- Urudu
- Vietnamese
- Welsh
What Languages are Supported for Human Translation in Globalization Pipeline?
Globalization Pipeline will support translation requests in the following language when you submitting a TR:
- Afrikaans
- Albanian
- Amharic
- Arabic
- Armenian
- Azerbaijani
- Bangla
- Basque
- Belarusian
- Bosnian
- British English
- Bulgarian
- Canadian English
- Canadian French
- Catalan
- Central Kurdish
- Montenegrin
- Croatian
- Czech
- Danish
- Dutch
- Estonian
- European Portuguese
- Filipino
- Finnish
- Flemish
- French
- French
- Georgian
- German
- Greek
- Gujarati
- Haitian Creole
- Hebrew
- Hindi
- Hungarian
- Icelandic
- Igbo
- Iloko
- Indonesian
- Irish
- Italian
- Japanese
- Javanese
- Kannada
- Kazakh (Cyrillic)
- Khmer
- Korean
- Lao
- Latin American Spanish
- Latvian
- Lithuanian
- Macedonian
- Malagasy
- Malay
- Malayalam
- Maltese
- Marathi
- Mexican Spanish
- Mongolian
- Nepali
- Norwegian Bokmål
- Pashto
- Persian
- Polish
- Portuguese
- Punjabi
- Romanian
- Rundi
- Samoan
- Serbian
- Serbian (Latin)
- Simplified Chinese
- Sinhala
- Slovak
- Slovenian
- Southern Sotho
- Spanish
- Spanish (Colombia)
- Swahili
- Swedish
- Swiss French
- Swiss High German
- Tajik
- Tamil
- Telugu
- Thai
- Tibetan
- Traditional Chinese
- Traditional Chinese (Hong Kong SAR China)
- Turkish
- Turkmen
- Ukrainian
- Urdu
- Uyghur
- Uzbek (Latin)
- Vietnamese
- Welsh
- Zhuang
- Zulu