Documoto Language Support

To support users worldwide, Documoto custom fields and content can be translated into over 20 different languages. Documoto also offers user-interface (UI) translations for Documoto defined labels throughout the application in 15 different languages.

Article Topics

• Types of Translations in Documoto
• User-Interface Translations
• Content Translations
• Supported Translations in Documoto Rocket & Publisher / Admin

Types of Translations in Documoto

Documoto supports two types of translations:

1. User-interface (“UI”) translations
2. Content translations

User-Interface (“UI”) Translations

User-interface translations translate all Documoto user-interface elements, such as: buttons, labels, tabs, etc., into the supported locale, or “language”. Note: UI translations extend to all modules (e.g. library, administration, reporting, etc.).

To enable a UI translation, a user can select the preferred language from the drop-down on the login page or set/update a preferred language in Account > Settings > Preferences. Note: once a language is selected, if the language is a UI supported locale, Documoto will automatically translate the user-interface.

Note: Documoto does not support user-interface translations for any of the following languages:

• Czech
• Hungarian
• Bahasa Indonesia
• Norwegian
• Romanian
• Serbian
• Ukranian

Please see the table below for a full list of translations supported in the Rocket Library user-interface and in the Publisher and Admin modules.

Content Translations

Content translations allow publishers to add translations for content that has been published to Documoto, as well as custom fields that have been created by administrators (e.g. tags, media categories, etc.).

In order for content display names (e.g. parts, pages, chapters, books, etc.) to be displayed a translated language, a publisher must add translation(s) to the properties for that entity.

Note: if a user changes their language preference, but content or custom fields have not been translated into that language, the UI will utilize the following fallback logic to translate content:

1. If content or custom fields have not been translated into the user’s language preference, then display the tenant default language/locale.
2. If content or customer fields have not been translated into the tenant’s default language/locale, then display the English translation.
3. If an English translation does not exist, then display the first available translation.

Supported Translations in Documoto Rocket & Publisher / Admin