Language solution for end-user documentation

[Fredrik Eskeland]

We have a end-user support manual which is maintained through confluence. 
Its become a need for this documentation to support multiple languages. 

Anyone have experiences on how to best deal with this?

have been looking at variants through Scroll Documents. But its seems like this is mostly a tool to create variants of the same source of documentation. Considering our need is langauge based, it would require different language source material. Although variants mostl likely is helpful to compare and help maintain articles, I am unsure if it would be the best solution for our needs. 

it would contain all the same source pages, just translateed versions which would have to be maintained along side the main documentation. 

[Kristian Klima]

Hi @Fredrik Eskeland 

You're close to the solution ;) 

You can extend the Scroll Documents app with Translations for Scroll Documents by K15t (same vendor).

I used a previous version of the app (for Scroll Versions...) and it worked like a charm. Basically, you export XLIFF files, have it translated, import translated XLIFFs back and that's it.

I think the app supports in Confluence translations as well.

(We actually used it alongside Variants and it worked beautifully as all Scroll family apps are integrated. Naturally, we published our docs in Scroll Viewport).

Here's the documentation for the Translations app - 

https://help.k15t.com/scroll-docs/3.24/cloud/manage-translations

[Max Foerster - K15t]

Hey @Fredrik Eskeland

Max from K15t here. :) Since you have already looked into variant management, I assume that you are already using Scroll Documents to manage your documentation. And you had the right instinct, there's the extension app called “Translations for Scroll Documents” to author and translate your documentation in different languages - either directly in Confluence or by collaborating with translation professionals using XLIFF. The translations fit seamlessly into your existing versions and variants setup in documents and can be published to Viewport just as easily.

If you have additional questions, feel free to drop them here. Additionally, you can contact us in our support on https://help.k15t.com/ or schedule a demo directly on our website to look into your use case and requirements. 

Let me know if you have additional questions, and have a wonderful start to your week. :)

Best, Max

[Mattia _bitvoodoo ag_]

Hello @Fredrik Eskeland

Welcome to the community. 

Our blog post on this topic could be a helpful first step.

Kind regards,
Mattia