In the projects view right click your project, chose Batch Tasks and run the task called "Finalize".

Jerzy Czopik said:

In the projects view right click your project, chose Batch Tasks and run the task called "Finalize".

I'd be curious to know the filetypes first... and as a general rule I never recommend that task to users.  You can do it of course, but it just carries too much baggage and is unnecessary unless you have a good reason for using it such as wanting to close your project, update your TMs, and generate lots of target files in your project.

Dear Paul

There is no general rule on that, unfortunately. Depending on the customer, you may be requested to deliver just the return package or the package AND fully formatted target files (very often in my case). And in case of other customers you may be asked to translate a file with no mention of CAT–the customer here awaits the delivery in the same format as the source, fully formatted and edited. So "Finalize" is the right task for that.

Best regards
Jerzy

Maybe... if there was one file I'd just use Shift+F12. Faster than a batch task and doesn't close the project down.

Still curious though... also unusual to hear this terminology "clean files" which is why I wondered what the source files were.

Paul said:

also unusual to hear this terminology "clean files" which is why I wondered what the source files were.

Well, people still live in the Trados time...

To use "Save target as" (in my case F12) you have to have the files open and then you need to confirm the name of each and every single file... Not convenient at all. Batch is much better. The best solution would be, if after the batch Studio wouldn't point to the target files, but kept focus on translatables. A corresponding idea is already there.

Using "Save target as" is far too simple, if you go through the whole process with translation and revision in projects with Project TM. In such cases you have to update your main TM.

I did say this Jerzy...

Paul said:

if there was one file

Simplistic maybe... but single file projects are a staple diet of our userbase. It's easy to confuse this group unnecessarily and make a simple process far more complicated than it needs to be.

But I take your point... just wish you'd take mine ;-)

Point taken. You have a far more wider view on what happens in the community than myself ever could have.

But I differ slightly on confusing, I would name this educating. Understanding processes is crucial for working with Studio. Using simple methods is a good approach, but it works much better if you also know the complicated paths. If you just know the simple part, you very likely get confused by an uncomplicated request involving only one or two steps more.

Point taken. You have a far more wider view on what happens in the community than myself ever could have.

But I differ slightly on confusing, I would name this educating. Understanding processes is crucial for working with Studio. Using simple methods is a good approach, but it works much better if you also know the complicated paths. If you just know the simple part, you very likely get confused by an uncomplicated request involving only one or two steps more.

Jerzy Czopik said:

Understanding processes is crucial for working with Studio. Using simple methods is a good approach, but it works much better if you also know the complicated paths.

Agreed.