We use Tridion Docs for content management and Trados for enterprise translation.  When a translation job is created directly in Trados, this is an option to add reference documents (instructions, English version content, style guides, etc.) for the LSP for reference.

When a job originates in Tridion Docs, it removes this valuable option to provide related information to the LSP.

This ticket requests two possible options for including designated reference documents in a Translation job for consideration:

1) Simple inclusion

 - This would take the form of being able to navigate to a designated folder within Docs and select objects to include with the translation job and have them specifically designated as reference docs in the job, rather than objects/assets to be translated.  These would be associated to the job in Trados and would not be created as tasks.   It is likely that these would primarily be PDF, Word docs, or other "Other" type objects within Docs.


2) Include published English content as reference

- This would be an option available when creating a translation job from a Publication Object.  The translation job creation process would allow the choice of an output type and would include the english version of the output in that type as a reference document.