Lucía LB 

I’d follow a different and easier approach: when you receive the return package from your translator, I’d remove the TM there (the one wihout password) from the project settings, and then add the password-protected one, so that TM will be updated with the content of the files.

Jesús Prieto  thank you for your quick answer!

That is a very good idea for updating the memories, I am sure it will be useful in other cases. It could be a solution here, but only after the documents are revised (we do not feed the TMs with the version received from translators), and that might imply also several steps.

Then, my question is whether there is a way to include TMs in packages while keeping their protection. Is this possible at all? Maybe I'm missing any detail in the setup.

Thanks!

 Lucía LB 

Sorry, I thought you were asking something else. I don’t use password-protected TMs, but I quickly tested they are not included (I don’t know why they are not inclued in the package nor if there is way to include them).

I guess you can use a project translation memory (not tested though):

If you want other colleagues to answer your question, don’t forget to reject my answer above.

Jesús Prieto 

Thank you for the idea. I tried that setup as well in the package creation and the password-protected TMs are not included either.

I will reject your answer, as you say, to see if someone else has any other suggestions.

Thanks again!

Lucía LB 

Lucía LB said:

I tried that setup as well in the package creation and the password-protected TMs are not included either.

I’d expect a project TM included in the package. That project TM will have all the translations needed for that particular project. Do you mean that no project TM is icluded in the package?

Jesús Prieto 

That is right! I tried again your setup (Create a new file-based project TM for every package) with a project which contained protected and non-protected TMs. The result was that the only translation memories reflected in the downloaded project were the non-protected ones.

Anyway, thanks for the ideas! For now I will keep updating the non-protected copies of my TMs by exporting the TMX and then importing. It's also a good way of having regular backups.

Jesús Prieto 

That is right! I tried again your setup (Create a new file-based project TM for every package) with a project which contained protected and non-protected TMs. The result was that the only translation memories reflected in the downloaded project were the non-protected ones.

Anyway, thanks for the ideas! For now I will keep updating the non-protected copies of my TMs by exporting the TMX and then importing. It's also a good way of having regular backups.