For WPF Passolo is using the LocBaml approach from Microsoft. It extracts the BAML streams from the binary. Prerequisite to localize a string is that it need to have a x:UID.

Developers can create UIDs while designing the form, you can also let the compiler create UIDs automatically. The Best practices chapter in https://docs.microsoft.com/en-us/dotnet/desktop/wpf/advanced/wpf-globalization-and-localization-overview?view=netframeworkdesktop-4.8 describes it more detail.

The impact of having no UIDs in Passolo is that you might see the WPF dialog in Passolo in its visual view but you can’t localize any of the seen string entries.

Let your developers create UIDs for localizable string entries or let the compile process do that automatically.

For WPF Passolo is using the LocBaml approach from Microsoft. It extracts the BAML streams from the binary. Prerequisite to localize a string is that it need to have a x:UID.

Developers can create UIDs while designing the form, you can also let the compiler create UIDs automatically. The Best practices chapter in https://docs.microsoft.com/en-us/dotnet/desktop/wpf/advanced/wpf-globalization-and-localization-overview?view=netframeworkdesktop-4.8 describes it more detail.

The impact of having no UIDs in Passolo is that you might see the WPF dialog in Passolo in its visual view but you can’t localize any of the seen string entries.

Let your developers create UIDs for localizable string entries or let the compile process do that automatically.

Dear Mr. Herrmann

thank you for your reply that reflects a thorough understanding of localization.
I have exposure only to the Passolo user interface, and regrettably, I have little knowledge of what is underneath in this process.
Thus, I suspected the cause to be in Passolo.
I will inquire at our developers.

Kind regards
Frank