Start a new topic

Transit PPF packages - which workflow is correct?

Hi everyone!


I've found two descriptions of the workflow for translating Transit PPF packages.


The first one is contained in this reference document:
https://github.com/idimitriadis0/TheCafeTranFiles/wiki/4-File-formats

There, it says that the workflow was copied verbatim from the other description, which is contained in the Knowledge Base:
https://cafetran.freshdesk.com/support/solutions/articles/6000186095-translation-of-ppf-packages


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!
Martin


/SOLVED

1 person likes this

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!

Irene

Perhaps it is tpf.zip with zip hidden? Check via Cmd+I
Not sure what you mean by this. Is there a specific way to rename the zip folder? I just replaced .zip by .tpf

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.

Answering for Irene: it’s an automated workflow so she has to upload to a portal. An incorrect file name or extension is all I can think of. Perhaps the portal expects TPF instead of tpf? Those f*cking portals!!!!
Could be the fact that you zipped on macOS, using the default zip app. Try on Windows or with a tool like Commander One https://mac.eltima.com/file-manager.html or WinZip for Mac.

Thanks! I'll try WinZip for Mac and keep you posted ...

WinZip didn't work either, too bad!

Next guess: the clm expects a different name of the return package? You’ll soon know the answer :)
What does clm mean here? Do you happen to know the name of the clm system?

CLM WebEdit

Ah, from the makers of Transit.
Login to post a comment