Best way to do a review between in-house translators

Hello,

I'll be doing some reviews for other Trados users in my company and though I've played around with checking xliff files, they've usually been after the translation had been produced and was just to update the TM data. So, could someone point me in the right direction for simple, step-by-step directions for how to send (share?) a file for review, then how to open it, then how to send it back, have the original translator reflect the changes, then generate the target.

We use Studio 2017 and we have shared folders we can access. We don't use Groupshare and all TMs+TBs are locally stored. I'd prefer not to use the "export to review document" because we wouldn't have the valuable TM/TB and verification functions available in the Editor view. 

Should projects packages and return packages be made? (Prefer not as the translators are relatively inexperienced with trados)
Should we just share the contents of the project folder? I'd open the project then inevitably get a bunch of errors saying it can't find the locally stored TM. Then I'd review it, save, then return the.... entire project folder back? Or just the xliff? Then they'd get a bunch of errors too when opening their project saying they can't find the locally stored resources I had on my computer. See what I'm saying? I'd love for it to be as simple as "send me the xliff file then I'll send it back to you. Then double-click the xliff file..." but I fear it may be more complicated.

Ideas welcome.

Parents Reply
  • Evzen,
    Preaching to the choir here. Getting my other coworker to use and learn about the software has been like pulling teeth. That's another story though...
    As for my situation, I'm hoping the translators can at least get a project started and use the instructions I've sent them for configuring their resources on their own. Then they'd just send me the xliff to review, and I'd reconfigure things. Not an issue on my end. If the translators still can't figure it out, I'd have to get my hands on the source file then make packages for them, then explain how to open and send them back. There's no way I'd be able to explain to them how to make a package to send to me. Baby steps...
Children