Translating documents: choosing between the Language I/O Translation Portal and Attachment translation

Translating documents

Language I/O offers several ways to translate files and documents (that is, images, PDFs, slides, etc.). One option is to use the Language I/O Translation Portal, and the other is with the Salesforce Case Attachment Translation feature, or you can attach files to translate directly with API calls. Each option comes with its strengths and benefits, tailored to certain scenarios.

Language I/O Translation Portal

Use the Translation Portal when you want the option of Machine Translation Post-Editing (MTPE), glossary imposition, or pre-processing of documents that are destined for publication. This is a great option for projects that you wish to be reviewed by professional translators, and do not require instant delivery. 

Attachment Translation (Language I/O apps and API)

Attachment translation in Salesforce Case or through the Language I/O API is a feature directed mostly at internal users (typically agents) to help them quickly understand the contents of a file. This features offers a quick translation solution: this means that the priority is instant results, which may cause unpolished output (such as formatting distortions or artifacts). Agents can highlight or copy the resulting text for use in their replies or comments.

Supported formats

Supported file sizes

• Translation Portal: The Portal supports file sizes of up to 500Mb
• Attachment translation: For attachments, file size is limited to 20Mb within Language I/O applications, 6Mb when using the API.

Known limitations:
* limited to 20 pages per document
** static gif only, not animated