Translating documents: choosing between the Language IO Translation Portal and Attachment translation

Translating documents

Language IO offers several ways to translate files and documents (that is, images, PDFs, slides, etc.). One option is to use the Language IO 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 IO 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 IO apps and API)

Attachment translation in Salesforce Case or through the Language IO 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

"Machine Translated" watermark

Whenever possible, the translated document will show a disclaimer to let the user know that the file was machine translated, with as much information as possible. For example, if the document was translated with Google, the disclaimer may look like this:

Language IO can currently show this disclaimer in PDF files, but not in DOCX or PPTX files.

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 IO applications, 6Mb when using the API.

Known limitations:
* you must specify a source locale to translate spreadsheets. Note that complex spreadsheet layouts (such as formulas, data tables, multi-column layouts, and graphs with labels or legends) may lead to formatting loss. 
** limited to 20 pages per document
*** static gif only, not animated
 

Important: Translated images such as JPG files may show visual artefacts next to the translated parts of the image. This is a normal occurrence caused by the automated Optical Character Recognition (OCR) process. While most differences do not impact the agent’s ability to understand the content, in some instances they might need further guidance. 
For example, formatting elements like strikethrough text (like this ) might not be rendered correctly after OCR processing. 
  
Language IO recommends that agents double-check the translated files and compare the formatting from the translated version to the original if there are questions.