Introduction to Multi-Language Documents

A Multi-Language Document is an output document that's linked to a Multi-Language FormClosed 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.. You can set up a Multi-Language Document to render in the languages that your field users, systems, and customers need. For example, if your company uses Spanish, and your customers use English, set up a document to generate a file for each language.

This topic lists the types of documents that support multiple languages and describes how the content in a Multi-Language Document is translated.

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

Essentials
Advanced +Add-on
Enterprise +Add-on

Contents

Types of Multi-Language Documents

The following document types support multiple languages.

How the system translates content in a Multi-Language Document

Standard PDF, Microsoft Word, and HTML document translations

Standard PDF, Microsoft Word, and HTML Multi-Language Documents include five different types of translatable content, as shown in the following example.

The following table lists each content type and how to translate it.

Content How to translate it

Form content:

  • Page and section headings

  • Question text

  • Manually-defined display values in lists for options-based questions

  • Question help

  • Custom validation messages

 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.
Answers from a Data SourceClosed 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.
Submitted data The document shows the answers exactly as the user entered them.
Metadata labels and other system-generated content, such as page numbering The TrueContext system has translations for these values in all supported languages. These values render in the translated language. You don’t need to perform any extra setup.

Details entered when setting up the Document:

  • Output File Properties (Title, Subject, Keywords, Author)

  • Document Header

  • Document Title

  • Additional Information

  • Footer

  • Table column headers set in the 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.

Tip:If you don’t have any content to translate, you don’t need to set up Additional Languages. 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 DRELClosed Data Reference Expression Language (DREL) is used to get form data and metadata and add it to a string, such as dates, usernames, or answers to questions in forms., you don’t need to set up translations. The system has translations for the rest of the document content, including metadata labels and other system-generated content.

XML and JSON document translations

XML and JSON documents don’t require any setup to be translated. These documents have three different types of content, as described in the following table.

Content Translation

Form content:

  • Page and section headings

  • Question text

  • Manually-defined display values in lists for options-based questions

  • Question help

  • Custom validation messages

 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.
Submitted data The document shows the answers exactly as the user entered them.
Key names and Question Unique IDs

These are not translated and remain the same across all languages.

Tip:For your integrations, map to the question Unique IDClosed 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., which doesn’t change, and not the question text.

Info:These details apply to JSON and XML documents you create and the standard JSON and XML documents you can download on the Form Submission Details page.