.dll source files, Passolo 2016, Studio 2022

Question

Hello, 
 We never receive requests for Passolo translations but now one of our biggest clients sent us first an .xml file (export) full of tags and then a Passolo .tbu file which we cannot open. 
 Our free Passolo version is old, from 2011... 
 Could the client send us the original .dll files? Can they be translated with Studio 2022? 
 I also installed Multilingual XML File Type in our Studio 2022. 
 Could we create a custom file type to filter the tags and still translate his .xml file in Studio 2022? And how can we create a custom file type? 
 Moreover, we don't have translators who use Passolo. What would be the best solution in this case? 
 Many thanks for your reply. Veronika

Achim Herrmann · Answer

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&rsquo;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.

Passolo > 1. General

.dll source files, Passolo 2016, Studio 2022