Accepted, Not Yet Planned

Hi Frank,

As we continue to pursue our "Convergence" strategy, more and more of the core language capabilities for SDL TMS will be delivered through SDL Language Cloud. SDL TMS will ultimately use SDL Language Cloud as the repository for files and projects at which point translators will have the option to either download a Studio package the contains all necessary settings or even be able to connect directly from Studio to open the cloud-based content. Once this is in place, we will have addressed this requirement I believe. I don't yet have a concrete release for such functionality but the status of "Not Planned" means that we will do it in a future release and the exact delivery vehicle is still to be determined.

Regards,

David

Studio project packages downloadable from TMS should automatically contain all relevant file type settings like in WorldServer packages

Like WorldServer, TMS should have an automatic mechanism that makes sure that Studio project packages that you download from TMS or transfer to Groupshare will always contain all relevant file type settings in the project settings.
Config-specific Studio project templates are often not created and can be a lot of work to update 10-20 Studio project templates, just because an Options XML file needed to be updated.

I am thinking about a mechanism that would monitor all configs that simply contain the default Studio project template.
Each time a TMS specialist would add a new file type (related to an Options XML) to a Config and each time he would update Options XML resources, TMS would automatically update all relevant Config-specific Studio project templates, so that in future Studio project packages, all file type settings would be up-to-date.

This would avoid frequent warnings: "This file was created using a file type definition that does not exist on your system"