Skip to main content

Manage a Translated Space

In this article, you’ll learn how the setup of a translated space differs when it’s managed by Scroll Translations versus Scroll Documents and Translations for Scroll Documents.

Space Setup with Scroll Translations compared to Scroll Documents

The table below outlines the differences in space setup between Scroll Translations and Scroll Documents:

A Scroll Translations managed space

A Scroll Documents managed space

Page tree

When you activate Scroll Translations in a space, it becomes active for the entire space, and you can translate all pages within that space.

On the other hand, Scroll Documents and its extension apps can be enabled for different scopes within the space, such as:

  • a single page in a space page tree

  • a sub-set of the space page tree,

  • or the full/entire page tree in a space.

During the conversion to Scroll Documents, you will also be introduced to versioning and the Working version:

  • If you convert a space using only Scroll Translations, a Working version will be created that includes all languages and previous translations.

  • If you convert a space using both Scroll Translations and Scroll Versions, a Working version will be created in the authoring language. Any selected versions will also be recreated and include the authoring language along with any existing translations. Each version and language will have its own page tree for managing content within the space.

In the following article, you can explore the differences in the translation workflow between Scroll Documents and Scroll Translations: Manage Manual and External Translations

Language setup

The language setup in both apps is quite similar. In Scroll Translations, the initial language you establish is known as the "default language." Likewise, in Scroll Documents, there is a base language termed the "authoring language." In both apps, all subsequent translations are built upon this initial default/authoring language. However, in Scroll Documents, XLIFF translations can also be based on a non-authoring language.

Language storage

In Scroll Translations, translations of a page are stored in dedicated language macros on the same page. These macros are usually not visible to the authors, but are automatically displayed depending on the selected language.

In Scroll Documents, each language has its own page tree, and translations are directly added to the Confluence page.

This has the advantage that translated page titles are discoverable with Confluence Search, while this is not the case with Scroll Translations managed spaces.

Language picker

In Scroll Translations, you have access to a language picker in the Scroll navigation bar. In the Confluence page view, you can see how the page content changes to reflect the selected language.

In Scroll Documents, the language picker is located in the Document toolbox and enables you to switch to the selected translation of a page. Additionally, Scroll Documents provides a Document Reader where you can switch between languages when consuming content within Confluence.

If you want to share your translations on a public website, you can use Scroll Viewport. To learn more, see: Publish Translations

Translation statuses

In Scroll Translations, you have the following translation statuses:

  • Translated

  • Outdated

  • Not translated

In Scroll Documents, there are two translation statuses which are applied as labels:

  • Translated

  • Needs-translating

During the conversion to Scroll Documents, the previous statuses will be transformed as follows:

  • Translated (remains the same)

  • Outdated (converted to "Needs-translating")

  • Not translated (converted to "Needs-translating")

For more information see: Track Translations in Scroll Documents

JavaScript errors detected

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

If this problem persists, please contact our support.