Integration between Trados and Confluence

Question

I work in a company that uses Trados and Confluence to manage translated documentation. But exporting the document from Confluence to a Word format in order to translate it in Trados makes us lose a lot in terms of configuration, macros etc. Is there a way to use Trados and Confluence together without this loss in configuration?

Lydia Simplicio · Answer

Thayna Souza while I am not a developer, I can confirm the following: 
 The idea of collecting source content and automating project creation is something the API's can do The idea of collecting source content and push/pull into Trados for project creation is a concept, where we have loads of examples. 
 These are often referred to as connectors and while we have some that are "out the box", I am not aware of any that originate from Confluence. 
 I assume confluence has API's and if yes then I believe you have all you need to get going. I would think the workflow for you would be: 
 
 User identifies which confluence page needs translating 
 Confluence pages has a "click to translate button" 
 Connector performs all the tasks required to get the content into a translatable format (in your case you mentioned MS Word) 
 Project in Studio is subsequently initiated 
 
 The alternative which I dont suspect is feasible due to the nature of confluence/my limited understanding of confluence, is for source content to automatically be identified and pulled in for translation. That said, other platforms (Content Management Systems) are equipped for that sort of workflow and there are connectors that specialise for this type of push/[pull workflow. 
 This leads onto my last point that you may need to think about. Is your connector just to push content for translation? Or will your connector pull the translations back in? If yes, then what would be parameters/logic be that would support this? Another area you may want to review is if a particular confluence page requires localisation, is the goal to have "human" translations at all times where you have target versions at all times? Or is it worth also considering having NMT integrated for "quick translation" where users have the option to apply MT all be it temporary to simply understand the content while they are actively looking at it. 
 I have included the link to our API documentation: https://developers.rws.com/ 
 Just a few clarifications and thoughts from my experience I thought I would share with you 
 Lyds

RWS AppStore > 1. General

Integration between Trados and Confluence