Daniel McCosh

I may be over simplifying this problem, but perhaps you can use the Bilingual Excel filetype instead and then you can just save the target file for review?  I don't know how complex the CSV is but this way you might just have to add a column for the project so it contains the target, then remove the source column when you are done.

The comments will be in the file by virtue of the fact you are actually sharing the target file for review and not an extract created from Studio.

If this doesn't work the only other way I can think of, aside from development, would be use one of the AHK scripts created by as he created some useful scripts for putting SDLXLIFF content into Excel.

Daniel McCosh

I may be over simplifying this problem, but perhaps you can use the Bilingual Excel filetype instead and then you can just save the target file for review?  I don't know how complex the CSV is but this way you might just have to add a column for the project so it contains the target, then remove the source column when you are done.

The comments will be in the file by virtue of the fact you are actually sharing the target file for review and not an extract created from Studio.

If this doesn't work the only other way I can think of, aside from development, would be use one of the AHK scripts created by as he created some useful scripts for putting SDLXLIFF content into Excel.

Thanks Paul! Both suggestions were helpful for different reasons. Kelly Edward's AHK script was really handy https://community.sdl.com/product-groups/translationproductivity/f/autohotkey/27197/to-extract-12-items-from-a-sdlxliff.