|
author |
|
|
|---|---|---|
|
header_image |
|
|
|
videoId |
|
|
For large collections of documentation in multiple languages, you can use a separate space for each language.
When using a space for each language, there are a few things to consider:
Translating
When your team changes documentation in one language, it’s important that changes are translated to other languages as well. Here are a few tips for making sure changes are made in every language:
-
Use a hidden Page Properties macro on each page to link it to all related pages in different language spaces. This can help your team identify all the pages to translate.
-
Create a strong manual process for updating all other languages when a page is changed
-
Use an app that automates translations workflows like Scroll Versions or Comala Workflows
-
If your team translates within Confluence, use browser windows side-by-side to view the source language next to the language you’re updating.
Multiple Versions and Languages
Since many approaches for versioning content involve using multiple spaces, using a space for every language adds a layer of complexity. To do make this work, you need to create additional space copies to represent all version and language combinations. For example, if you have a version 1.0 and 2.0, and write in English and German, you might create the following spaces:
-
1.0 English
-
1.0 German
-
2.0 English
-
2.0 German
Your team will also have to manually ensure that both the English and German spaces are updated for each new version of your product. With a solid manual process, your team can make this work. Just keep in mind that complexity increases for every additional language and version.
Learn more about .
Keep in Mind
-
Using one space for each language provides your readers a place where they can read content fully within their own language, which is a great experience.
-
Users will need to navigate to the correct URL for documentation in their preferred language.
-
Managing multiple languages requires a stringent manual process to ensure no translations are missed. Especially when also working with multiple versions.
-
This approach requires you to do all translation in Confluence, and doesn’t support working with an external Translation Management System.
