Publish Translations

Publishing multilingual content is necessary for effective technical documentation and enables you to better serve a variety of audiences. Scroll Translations has been widely used for this purpose, offering various publication methods in combination with other Scroll apps such as Scroll Versions.

However, there are differences when converting to Scroll Documents. This article explains the changes in publishing options for multilingual content when converting from Scroll Translations and Scroll Versions to Scroll Documents and its extension apps.

Use cases

Scroll Documents and its extensions are currently optimized for the following use cases:

• Product documentation

• Internal knowledge bases and manuals in Confluence

If you feel the app lacks features to help support your use case, don’t hesitate to reach out to our support team for feedback: help@k15t.com

Publishing Options with Scroll Translations

When using Scroll Translations, content can be published in the following ways:

• Online help center: Deliver content to an internal or public help center site with Scroll Viewport. This could be alone or in combination with Scroll Versions.

• Offline manuals: Publish to offline formats such as user guides or manuals with Scroll PDF, Word, or HTML Exporter.

• Multilingual intranet: Deliver a multilingual intranet by publishing translated content to a new space with Scroll Versions or saved within Scroll Translations-managed spaces.

Publishing Options with Scroll Documents

Scroll Documents offers the same flexible publishing options for your translated content as Scroll Translations:

• Online help center: Create a user-friendly help center with Scroll Viewport, complete with a language picker for easy access. You can choose to publish a single version or multiple versions of your translations.

• Offline manuals: Generate PDF, Word, or HTML manuals in various languages using Scroll Exporter apps.

• Multilingual intranet: Publish translated content within Confluence, either to a dedicated space or within your current space.

Key Differences for Multilingual Intranets in Scroll Documents

If you're using Scroll Translations for a multilingual intranet, you'll notice these key changes after converting to Scroll Documents.

Publishing to another space

• Publishing multiple languages: You can only publish one language at a time to the same target space. To publish multiple languages to the same space, you'll also need to use prefixes to differentiate them, as each language has its own page tree.

• No language picker: In the target space, readers access languages directly via the page tree, without a language picker.

Recommendation
For optimal user experience, publish each language to its own dedicated space.

Publishing within the author space

• Dedicated page trees: Each language version has its own page tree which can be navigated using a version and language picker.

• Language picker access: The language picker is available in the Document Toolbox and Document Reader, but not in the default page view.

Conclusion

Scroll Documents and Scroll Translations offer the same publishing options. However, if you're using Scroll Translations for a multilingual intranet, be aware of the listed key changes after converting to Scroll Documents. To see how these changes might impact your specific setup, we recommend running a test conversion.