Hi everyone, currently we are checking if we can use confluence to create PDF manuals. The documentation must be multilingual and the translation tool is Trados. Does anyone have experience with this issue and help us with recommendations. Our questions are:
- How to create multilingual content, as chunks in the page or in seperate pages?
- How to export content to Trados and read it back to Confluence?
AppFusions is deep in development of an "Enterprise Translation for Confluence Product Docs" solution, with expected GA release in Q2 (April/May).
The idea is using Confluence for your product documentation, where you would have a document, with many "chapters" per space - and then translate the space into different language "docs", at release time. A group of spaces, would make up the "doc set" (say user manual, admin manual, quick start manual, api manual), per release, also with each in many languages.
The benefit of a doc-per-space allows for per-doc search, permission controls, among other organizational reasons.
Iteratively over time, you can "train" the translation engine too (i.e., edit the translations from Confluence - which are saved back iteratively to the MT), so over time, your translations are tuned to the context of your product docs, terminology, and ultimately your company needs.
You have over 75 languages to choose from. Perhaps you only need a few - but hey, good to have options.
This tool will be Enterprise-grade - not using low-rate free/insecure translators like on the Internet.
One more thing - using Scroll PDF Exporter, you can also export your translated docs to PDF, as mentioned above - but you also have a RICH SEO-indexable online doc set, in as many languages as you wish.
If interested in this offering - love to show you in Beta, which is just starting now. Send us a mail and can get you going!
Hello Ellen, thanks for your answer.
I'm not sure, if this development covers the issues we need. In fact we don't need an integrated translation machine in Confluence. We are required to use the product Trados, because our complete translation is done using this tool: http://www.sdl.com/products/translation-management/
What we need is a xml-export/import of content and an idea how to organize the multilingual content.
Understand - no our solution is not using (or integrated with SDL's 2005 legacy CAT Trados product) - it is using newer technology, analogous to SDL's:
* WorldServer (which I hear is being discontinued..)
* TMS (which I hear is being discontinued)
* CAEF (SDLs current push product)
Ours is seamlessly integrated with LingoTek TMS (translation management system), with the CAT workbench integrated also in Confluence, so you can create the translation, and edit the translations and train the MT directly, all from Confluence.
Without getting into pricing right here, I can tell you absolutely you would save money, let alone latest tech (compared with Trados) since the CAT is included - and the Trados CAT you need to buy.
So if interested in evolving your processes to work with Confluence as a simple enterprise product doc translation engine/deployment platform, let us know - and we can get you going.
GA (ship) for our LingoTek TMS integration is firmly expected to be April 2013.
Good morning, After a long weekend cleaning up, I am still in the cleanup mode 😊. I am curious to know: When do you feel the urgency to cleanup your Atlassian Tools? How many times do y...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG