Hi Richard - did you use the "Save to Cloud" functionality in Studio 2022? It features a specific flow where you can open the package in Studio and then save it to cloud (right click on the name in the Projects view and choose "Save to Cloud". The package support in the browser does not yet have parity with the Studio flow and indeed may produce some additional files you don't necessarily need.

I was literally just trying that with a package that I completed. After completing it I saved it to Cloud but weirdly enough the cloud does not see it as completed? You'd assume it send the translated parts to the cloud as well?

So current workflow SHOULD be: open in Studio -> Save to Cloud -> Work in Cloud -> Create return package in Studio? Is there any indication on to if/when we can do it all in the cloud and don't need to use Studio to work on packages? It's just so weird that a Trados proprietary file cannot be used in Cloud. You'd expect that to be on top of the list really. 

Yes that should be the workflow - open in Studio, save to cloud, work in Studio or Online Editor/browser as you see fit (this is where the flexibility comes in), at the end create a return package in Studio, send back to your client. There are a lot of nitty-gritty details that Studio is natively aware of, where a cloud/browser-only solution is not as straightforward as one might think. So Studio/cloud combination is the recommended way of working here to roundtrip both files and settings as best as possible.

Am I right in thinking that where I work shouldn't matter, meaning if I create a project in the cloud, and work on it in Studio, it should simply update the progress in both locations? I just tested with a small file, created it in Studio in cloud (not local), confirmed the segments, but both Studio and Cloud show no progress, and the version in Cloud does not show any translated segments. So you can't switch between locations, depending on the need?

Hi Richard - once you save a file that is in a cloud (not local) project, it will update both locally + in the cloud and the project statistics should update in both places. In a cloud project, you should always be able to, say, switch freely between Studio and Online Editor - and the save action in Studio (or closing the Online Editor tab) will update the file information in the cloud, and Studio will then also check if a file has been updated in Online Editor and prompt you to download the latest version from the cloud. There are many such mechanisms when working in a cloud project.

Thanks, Daniel

Still trying this out. So I opened a package in Studio, saved it in the cloud, and worked on it in Studio. Translated one of the 19 files, it did not show as translated in the file overview, and it would not let me save it as target in Studio. That basically renders saving in the cloud as useless for me, as it also did not show up as translated in the cloud. Like I did the translation for nothing really. That cannot be how it's supposed to be. Is this just still very buggy or am I doing something wrong?

Hi Richard - I played with it and can confirm the progress information does not seem to be updated properly. I will report this to the team. I ran the "Translation Count" batch task manually in Studio and then it updated locally (but not in the cloud as this is a purely local batch task). To save target files, you can use the new batch task "Generate target files (cloud projects)", this should give you the target files for the project. We should also look at enabling the Save As Target command in the Editor. It should also be possible to use Create Return Package to send an updated package back. I agree there are some rough edges here and I will keep working with the team to refine, so these flows work better. Thanks, Daniel

Hi Richard - I played with it and can confirm the progress information does not seem to be updated properly. I will report this to the team. I ran the "Translation Count" batch task manually in Studio and then it updated locally (but not in the cloud as this is a purely local batch task). To save target files, you can use the new batch task "Generate target files (cloud projects)", this should give you the target files for the project. We should also look at enabling the Save As Target command in the Editor. It should also be possible to use Create Return Package to send an updated package back. I agree there are some rough edges here and I will keep working with the team to refine, so these flows work better. Thanks, Daniel

Thanks Daniel. I work on both desktop and laptop, so ideally I'd like to save everything in the cloud, work on whatever device I want at that time, continue on the other if needed, and save it in Studio to return it to the client. Not sure if that's something that is possible. I do use iCloud Drive for that now, and that works but I understood it's not always the most stable route to take.

That's totally how it should work, Richard - and the basic flow does work as far as I played with it just now. But it does have rough edges which we need to iron out for sure. Thanks, Daniel