TPF are return packages
PPF are project packages, that you may want to forward to another translator / a reviewer
I would have to test if the value in the tpf necessarily has to be changed or that Transit is tolerant here.
I just used the workflow described in the Knowledge Base but can't upload the .tpf package (greyed out so I can't select it). Any ideas where the problem could be?
Thanks for your help!
Yes, changing the extension of the .zip archive to .tpf is correct.
But where did you try to upload the file? Probably on a web portal that only allows files with certain extensions. Does the recipient also have an email address? Sending files with the .tpf extension by email is no problem at all.
Thanks! I'll try WinZip for Mac and keep you posted ...
WinZip didn't work either, too bad!
I've found two descriptions of the workflow for translating Transit PPF packages.
The first one is contained in this reference document:
There, it says that the workflow was copied verbatim from the other description, which is contained in the Knowledge Base:
However, there are differences between the two descriptions. According to the Knowledge Base, a value in the PRJ file must be changed, and the extension of the return package must be .tpf (according to the first description, the return package must have the extension .PPF too).
I've always used the workflow described in the Knowledge Base, and it worked fine. But to make sure, I'd like to ask if the workflow for PPF packages has changed in the meantime and the workflow in the Knowledge Base is not up to date.
TIA for your help!