How Multi-Language Documents Work

A Multi-Language Document is an output document that’s linked to a Multi-Language Form A Multi-Language Form is a form that’s set up with different translations so that field users can choose their preferred language. Translated content includes page and section names, question text, help text, and other form content.. The output document renders in the language selected when the form first opens. For example, if a user chooses to display the form in Japanese, the system renders the Multi-Language Document in Japanese. This topic describes how the system translates all the content in a Multi-Language Document. It also describes the high-level process that you follow to set up a Multi-Language Document.

Available as an add-on to the Advanced and Enterprise tiers:

Contents

• How Multi-Language Documents Work
• Example of a Multi-Language Document
• How to translate all the content in a Multi-Language Document
• Display all document details in the selected language
• Don’t display document-specific content in the selected language
• Types of Multi-Language Documents
• High-level process to set up a Multi-Language Document
• How standard PDF, Microsoft Word, and HTML document translations work
• How XML and JSON documents work
• Copy the configuration of a Multi-Language Document

Example of a Multi-Language Document

Multi-Language Documents give you a consistent workflow that includes submitted form content, data, and output documents in a single language. A Multi-Language Document renders based on the form selected language. The selected language is the language selected by the user, a dispatch, or an App‑to‑App call.

This example shows a standard PDF document rendered in Spanish where:

• The form selected language is Spanish.

• The document has Spanish as an active additional language with a translation file for document details.

The following image shows where the system gets translations for different types of content in the output document.

How to translate all the content in a Multi-Language Document

Display all document details in the selected language

D

1. Set up additional document languages.

2. Upload translation files as needed for the document details, such as headers and footers.

3. Make the additional languages active.

Don’t display document-specific content in the selected language

System generated content, such as metadata, always renders in the form’s selected language.

If you don’t provide translation files for additional languages, document details, such as headers and footers, default to the text entered by the document designer when they set up the document.

Types of Multi-Language Documents

• Standard PDF, Word, and HTML—Set up and activate additional languages.

• XML and JSON—No setup required.

• HTML output document within the Email Data Destination body—No setup required.

High-level process to set up a Multi-Language Document

1. Set up a Multi-Language Form.

2. Set up a standard PDF, Microsoft Word, or HTML document, and then select a Source Language. The Source Language indicates the language you used to set up the document.

3. Add Additional Languages to your document.

   Info:The topic Supported Languages for the Multi-Language Feature lists the languages you can add to Multi-Language Forms and Documents.

   When you add languages, the system generates an Excel translation file for each language. The translation file includes the strings to translate for any document details you entered. If you have content to translate, download the file, enter the translations, and upload it.

   Tip:If you don’t have any content to translate, you don’t need to set up Additional Languages.

   • Even if you don’t upload or activate a language, the system translates most of the document for you. The system automatically translates metadata and other system-generated content in your PDF, Word, and HTML documents based on the selected language. You don’t need to perform any additional setup.

   • You only need to set up translations if your headers, footers, properties, or other document details require translation. For example, if your document details only include DREL, you don’t need to set up translations.

4. Make the Additional Language Active when you finish uploading the translations.

5. Add the document to your form outputs. You can add it directly or as a Data Destination A Data Destination specifies where to send data from a submitted form. You can use Data Destinations to automate data sharing and storage, routing data to a specific service (such as email or cloud storage) in several different formats. attachment.

6. When a supervisor dispatches a form, or a user or App‑to‑App call opens the form, they choose the selected language. This is the language that the form displays in.

7. When a user submits a Multi-Language Form, the system combines the following data to produce a document in the selected language:

   • The form translation file for the selected language

   • The submitted form answers

   • The document setup

   • The document translation file for the selected language

     Tip: If the document doesn’t have the selected language set up as an Additional Language with a translation file, the system renders the document as follows:

     • The document metadata automatically renders in the selected language.

     • Document details, such as headers, footers, and properties, render in the document’s Source Language.

How standard PDF, Microsoft Word, and HTML document translations work

With the Multi-Language add-on, all system-generated content in your document is automatically translated. If you need to translate headers, footers, and other document details, you set up additional languages and upload translation files.

The following table describes how translations work for each part of the document.

Part of the Document	How the translation works
Metadata labels and system-generated content	The system automatically translates metadata labels and system-generated content into the selected language. You don’t need to perform any extra setup.
Output File Properties Header Title Additional information Footer Table column headers you set in your Table Layout.	Add an Additional Language. Download an Excel file that has the strings to translate, add translations, upload the file, and activate the language. Info:The topic Steps to Set Up Translations for a Multi-Language Document describes how to add translations in more detail.
Question text	When you set up a Multi-Language Form, you upload an Excel translation file to the form. The document gets the translated text from the form’s translation file.
Question answers	The document shows the answers exactly as the user entered them.
Answers from a Data Source Data sources, also known as "Lookups", are external sources of data that you upload or connect to TrueContext. You can reference this data in a form to populate answers or answer options. Data sources save typing, reduce errors, and make it easy to provide mobile users with only the relevant, most current data.	You can set up a Data Source to include data in multiple languages. Info:The topic Data Source Translations includes more details about setting up a Data Source in multiple languages.

How XML and JSON documents work

If an XML or JSON document is linked to a Multi-Language Form, the document displays form content in the form’s Selected Language. The document shows translated form content based on the form’s translation file. The key names and question Unique IDs don’t change. For your integrations, use the question Unique ID A Unique ID refers to the specific identifier of a question, form page, form section, or Data Destination. Unique IDs are used as reference points when pulling data for conditional logic, Analytics projects, Data Destinations, and Documents. and not the question text.

The system also translates the standard XML and JSON files that you can download from the Form Submission Details page. You don’t need to set up translation files for XML or JSON files that you attach or download.

Copy the configuration of a Multi-Language Document

Once you have a Multi-Language Document set up, you can copy its configuration to an existing target document. When you copy a Multi-Language Document configuration, you copy the document setup and any additional languages. This means that if your target document has any languages already set up, the source document languages will overwrite them.

Info:The section Create and Manage Documents: Copy Document configuration to an existing Document describes how to copy a document configuration in more detail.