Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
Translate C# WPF assemblies without source - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Mon Nov 6th, 2017 02:23 pm
PM Private Upload Quote Reply
s.evieux
Member
 

Joined: Mon Nov 6th, 2017
Location:  
Posts: 2
Status: 
Offline
Hello

I currently have a program built in C# WPF. It is written in English and already translated in 7 languages but I have no access to the source code nor to the sisulizer project file.
Is there a way to translate this sorftware in any new language just based on the assemblies I currently have ?

Thanks a lot

Back To Top PM Private Upload Quote Reply

 Posted: Mon Nov 6th, 2017 02:37 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3024
Status: 
Offline
Hi,

You can create a new Sisulizer projects from the binaries. Either Sisulizer detects the translations or you can import them.

The problem is, that your binaries are missing some information to build new binaries stored only in the project file. Depending on the structure of your project it might work or not without this info.

The easiest is to give it a try. Simply create a new Sisulizer projectband select the EXE as source.

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Mon Nov 6th, 2017 02:42 pm
PM Private Upload Quote Reply
s.evieux
Member
 

Joined: Mon Nov 6th, 2017
Location:  
Posts: 2
Status: 
Offline
Hi

Thanks for the answer...
The reason I posted is that this straight forward method did not give anything...

Seeing the directory structure and content of the application, I can see that 6 assemblies are translated (I can find the 6 corresponding satellites assemblies).

But if I load those main assemblies, the only translatable things Sisulizer shows are the  FileDescription, the LegalCopyRight and the ProductName.

I I try to add the satellite assemblies, I have a lot of error messages and Sisulizer finds much more to translate that what should be (bindings for example...)

And anyway, I did not find any mean to build from the slp...

Back To Top PM Private Upload Quote Reply

 Posted: Mon Nov 6th, 2017 05:27 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3024
Status: 
Offline
If your binaries are obfuscated Sisulizer will not be able to localize them. I ask our R&D if they have some hints...

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

Current time is 04:27 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Translate C# WPF assemblies without source



WowUltra modified by Sisulizer Copyright © 2007-09 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize