Transit Package Handler does not preserve folder structure from PPF

Hi everyone,

we've noticed that the Transit Package Handler plug-in does not preserve the folder structure that comes with a PPF.

In our case, we initially had two subfolders in the Transit project.

After unpacking the PPF in Trados Studio, the folder structure is gone both in the Studio project and the TPF file.

With these folders completely gone in the TPF (and all translation files put in the root directory of the package), Transit cannot overwrite the original target language files when importing the translations,

as it fails to assign the files to the correct subfolder. The target language files need to be overwritten manually then, which is rather time consuming.

We would appreciate if someone could have a look into this!

Many thanks in advance, best regards,

Julian

emoji
Parents Reply
  • Hello   ,
    I've tested the new 2024 plugin for the Transit package handler (TPH) and came across a few things that might be worth noting:
    a) By design, TPH does not import TermStar dictionaries included in the PPF, which would require translators to manually convert and add a SDLTB after the import
    b) TPH does not consistently detect Translation Memories included in the PPF. I didn't find any information whatsoever in the App Store documentation on how TMs (aka "reference material" according to Transit terminology standards) need to be structured in the Transit project to make TPH detect the files. Are subfoldfers allowed? Does it only detect reference material with a certain nomenclature?
    c) TPH regularly crashes when bigger PPF packages are imported, especially bigger ones. How can I provide you with the StarTransitLog.txt? I can't upload local files here.

    Thanks in advance for your feedback!

    KR,
    Julian

    emoji
Children