Skip to main content
Skip table of contents

Translate Reusable Content

Let’s say you're reusing content like images or text strings, such as addresses, that need to vary by language. In this article, we’ll walk you through how to set up a translatable include library to make it easy to localize reusable content like images or text blocks across your translations.

How Can I Translate Reusable Content?

To translate reusable content such as images, you need to create a dedicated include library within each translated page tree in a version. This setup must be done manually the first time for each translation, but once configured, you can reuse the translated content from the include library whenever you reuse translations from previous versions or update a translation through synchronization, no matter if you translate via XLIFF or manually in Confluence.

Each translated version will have its own include library within its page tree. This ensures that changes made to included pages in one version won’t affect earlier or later saved versions.

Please note

Since the include library is placed inside the translated Scroll Document page tree, any include macro referencing it will not be resolved. Scroll Documents only resolves included content that lives outside the Scroll Document page trees. For more information see: Version a Document That Contains Included Content

How to Set Up a Translatable Include Library

To create a translatable include library follow the process and steps listed below.

1. Create the include library in the authoring language

We recommend you start creating the include library within the authoring language in your Working version:

  1. In the Document Manager, locate the Working version.

  2. Navigate to the root page of the authoring language and create a new page, e.g., "_Include".

  3. Under this page, create child pages with the reusable content (e.g., images or text blocks).

  4. Use include macros to embed this content on relevant pages within the version.

2. Add translations

Before you can start translating the include library you created in the authoring language, you’ll need to add the relevant languages to that version:

When you add languages to a version, all pages from the authoring language, including the include library you just created, will be duplicated for translation.

3. Translate and apply reusable content

After applying the languages, and as a result copying the include library page tree, it’s time to translate and apply the content.

  1. Go to each copied page under the “_Include” parent page, in the language tree and update the pages with the content relevant for that language.

  2. Give the pages the TRANSLATED label when you are done.

  3. Go over the rest of the pages within the translated page tree, and include the localized content using the same macros as in the authoring l language.

  4. Ensure you mark the pages as TRANSLATED once you’re done.

Great!

You have set up your first translatable include library.

How To Reuse Translated Content in Future Versions

Once set up, your translated include libraries are preserved per version. When you save a new version and reuse translations, or use synchronization to update a translation, the translated include content will remain unchanged (as long as the included source page has not been updated).

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.