Working with Project TMs gives you the possibility to control translated segments before they are stored in a main memory, you want to keep clean. It's also a good way to send a project to a translator who can't stay connected to a main server TM: relevant segments from the main TM will be copied in the project TM and sent as a file in the project package. Be aware that working with a project TMs will prevent the translator from writing in the main TM.Updating both main TM and project TM is not possible.
If you decide to work with project TMs, you can use the batch task "Populate Project Translation Memories" either through the task sequence "Prepare"
or through the context menu of the project after creating it.
Project TMs are stored in the corresponding target language subfolder in the "TM" subfolder of the project folder and are named after the project name and the main TM.
But this is not obligatory: you can also prepare the project without project TM, and choose to include a project TM while creating the packages to be sent to your translators. In this case, the project TMs won't be stored in the project folder.
...Bugs in packages...
We discover recently a bug in our packages.
In the 4th window of the package wizard, you have 3 options connected to "Project Translation Memory":
It's important to use "Create a new file-based project translation memory for every package" if you want your translators to work with a project TM. Studio will create itself new project memories and inserts them in the corresponding package.
"Include the existing project translation memory in every package" doesn't work properly if you created a project with 2 or more target languages. Some Project TMs won't be included in the corresponding packages or a project TM with another language pair will be included, so that your translator won't be able to work with a TM at all.
If you prefere not to work with a project TM, choose the third option...