DLL is not DLL. While Passolo supports most development platforms, Studio just supports .NET DLLs. So you need to clarify how DLLs are developed before you can use Studio. Software manufacturers are choosing Passolo because it supports a project based workflow which’s allows to preserve previous translations instead of retranslating everything from the TM with each new software release.

Your customer should provide a TBULICxx file that would allow you to use the free Translator Edition. When localizing DLL based software, it is usually beneficial to be able to preview the dialog and potentially adapt control sizes when translations are getting longer.

Newer Passolo version are also supporting SDLXLIFF export/import workflows.

DLL is not DLL. While Passolo supports most development platforms, Studio just supports .NET DLLs. So you need to clarify how DLLs are developed before you can use Studio. Software manufacturers are choosing Passolo because it supports a project based workflow which’s allows to preserve previous translations instead of retranslating everything from the TM with each new software release.

Your customer should provide a TBULICxx file that would allow you to use the free Translator Edition. When localizing DLL based software, it is usually beneficial to be able to preview the dialog and potentially adapt control sizes when translations are getting longer.

Newer Passolo version are also supporting SDLXLIFF export/import workflows.

Hi Achim,

Wow, thanks for this explanation. :-)

So, can the client also make an export in .sdlxliff format himself?? He has Passolo v 16.

No, this feature is only available in Passolo 2018 and newer.

If the customer has no Team Edition and sends just TBU files he is expecting you to have a fully licenses Team Edition to split up the project for your supply chain.