Hi David,

Hmm, I just tested the roundtrip from Studio (2022 in my case) and the comments were always retained. What might be worth checking is to see if in your default file type configuration in the cloud, the setting "retain Studio comments in target file" is active. You'll find it under the Microsoft Word 2007-2019 file type. It was active in my case, but not sure if this is the default or not.

I did notice an oddity (but it did not seem to have any negative effect): when looking at project file type settings for the cloud project in Studio, I can see that the same option in the Word 2007-2019 file type settings is actually off (although it is on in the cloud). But when I ran the batch task "Generate Target Translation (Cloud)" the comment was there in the target file anyway. I did not use segment comments but rather range comments; not sure if that makes a difference.

In the Online Editor, there is actually a separate panel for entering comments - you'll see an icon with a speech bubble on the right hand side next to the other icons there. This will open the comments pane and you can enter comments there in a similar way as in Studio. But adding comments this way should work in both Online Editor and Studio anyway.

Another potential workaround - rather than running the Studio batch task, you can also download native target files from the Files area in a cloud project in the browser. Open the project and go to the Files tab. There you'll see your files and you can click the translated versions and then click Download. This will give you the option of getting bilingual (SDLXLIFF) or native target (.docx files). When I did this, the comments were also preserved.

So - just some hints and tips and hopefully this will work for you.

Thanks, Daniel