Hi Lucy Matticoli-Mason 

Unknown said:

QUESTION 1: Is it true that a file can be exported from Trados Studio to be sent for translation to a translator who doesn't own a CAT tool? 

Yes.  You can use the Export for Bilingual Review feature.  You do need to be careful with this though as it is normally used for light edits and not complete translations.  Perhaps review this article to get a feel for the pitfalls and ensure you avoid them:

https://multifarious.filkin.com/2014/07/26/efer-ad/

Unknown said:

QUESTION 2: If yes, do the steps below describe the correct workflow?

1) Create the project making sure to automatically copy source text into target segments.

2) Right click on project and select Batch Tasks > Export for bilingual review.

3) Send the exported files for translation. Once these files are received back from the translator, proceed to reimport them via Batch Tasks > Update from Bilingual Review

Yes.  You can also do this without the Batch Tasks if the file is open in the Studio Editor.  Under the Review tab you'll find these options:

The Batch Tasks is useful for two reasons:

1. You don't have to open the files to perform the action (although you probably should do anyway to check the file is ok)

2. You can export/import multiple files in one go

Unknown said:

QUESTION 3: How can this translator keep terminology consistent w/o having a TM or a terminology database?  Exporting MultiTerm and sending it as a glossary is an option, but it doesn't seem to be an efficient one. 

Without using any kind of tool for this it's all down to the efficacy of their own process.  Even if you give them an export in Excel they will still be applying this manually.  You can check their work when it comes back and then decide whether you are getting what you need.  I'm not going to comment on this as there are plenty of translators who believe they could do just as good a job without a tool as they can with it.  You will be the judge of that.

Unknown said:

I should add that this scenario is being explored for 2 diff projects: one project has only a couple of small Word documents, but the other one has a single-huge document containing over 30,000 words.

If they are only Word files the other option you have is to allow them to translate the Word file in Word the way they would always work without a CAT, and then you can align the source and target afterwards to get the content into a TM.  But again, this is going to add work for you not just in aligning but also in checking the quality and consistency of the work.

My personal opinion is that if I was using translation tools in my environment then I would probably not ask a translator who does not use CAT tools to handle a 30,000 word project.  I might with the smaller files if the subject matter was so unusual that I needed their specific expertise; and I might if the 30,000 word project was a one off like a literary translation for example where again I needed a very specific skillset.  But that's just me, and I'm interested in what others might have to say on this topic too!

Regards

Paul

Hi Lucy Matticoli-Mason 

Unknown said:

QUESTION 1: Is it true that a file can be exported from Trados Studio to be sent for translation to a translator who doesn't own a CAT tool? 

Yes.  You can use the Export for Bilingual Review feature.  You do need to be careful with this though as it is normally used for light edits and not complete translations.  Perhaps review this article to get a feel for the pitfalls and ensure you avoid them:

https://multifarious.filkin.com/2014/07/26/efer-ad/

Unknown said:

QUESTION 2: If yes, do the steps below describe the correct workflow?

1) Create the project making sure to automatically copy source text into target segments.

2) Right click on project and select Batch Tasks > Export for bilingual review.

3) Send the exported files for translation. Once these files are received back from the translator, proceed to reimport them via Batch Tasks > Update from Bilingual Review

Yes.  You can also do this without the Batch Tasks if the file is open in the Studio Editor.  Under the Review tab you'll find these options:

The Batch Tasks is useful for two reasons:

1. You don't have to open the files to perform the action (although you probably should do anyway to check the file is ok)

2. You can export/import multiple files in one go

Unknown said:

QUESTION 3: How can this translator keep terminology consistent w/o having a TM or a terminology database?  Exporting MultiTerm and sending it as a glossary is an option, but it doesn't seem to be an efficient one. 

Without using any kind of tool for this it's all down to the efficacy of their own process.  Even if you give them an export in Excel they will still be applying this manually.  You can check their work when it comes back and then decide whether you are getting what you need.  I'm not going to comment on this as there are plenty of translators who believe they could do just as good a job without a tool as they can with it.  You will be the judge of that.

Unknown said:

I should add that this scenario is being explored for 2 diff projects: one project has only a couple of small Word documents, but the other one has a single-huge document containing over 30,000 words.

If they are only Word files the other option you have is to allow them to translate the Word file in Word the way they would always work without a CAT, and then you can align the source and target afterwards to get the content into a TM.  But again, this is going to add work for you not just in aligning but also in checking the quality and consistency of the work.

My personal opinion is that if I was using translation tools in my environment then I would probably not ask a translator who does not use CAT tools to handle a 30,000 word project.  I might with the smaller files if the subject matter was so unusual that I needed their specific expertise; and I might if the 30,000 word project was a one off like a literary translation for example where again I needed a very specific skillset.  But that's just me, and I'm interested in what others might have to say on this topic too!

Regards

Paul