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.


 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius  
AuthorPost
ka_developer
Member
 

Joined: Tue Apr 20th, 2010
Location:  
Posts: 65
Status: 
Offline
Hello Sisulizer Team,

we need a few infos for better planning of our product localization in 2019.

Could you please give us some feedback on following topics:

1) Localizing of WPF C# applications: it's working well if we do it on visual studio solution and source code basis. Are you planning to make possible the localization of WPF on the basis of dlls only (as it was by winforms) or do you see the localization based on the source code as a final solution?
(For us it means that the localization for regional languages cannot be delegated to regional offices because we cannot give them the source code of our software.)

2) When approximately can we expect Sisulizer 5 and what could be an estimated cost of upgrading of version 4 to version 5?

Your feedback will be greatly appreciated.

Best regards

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3195
Status: 
Offline
Hi,
The recommended method is to localize the Visual Studio project file. But this does not mean, that source code is localized. Sisulizer still localizes the binaries it finds in the project files. Besides it gets more info not in the binaries from the project file. The translator does not need to see the source code. We hoped to get all info from binary but it would require to disassemble binaries. This is a complicated and b critical to legal concerns. So we get info from project file plus binaries.

While also possible, we do not recommend to localize source code.

We have no ETA for 5. In the past we charged 35% of a new license, except you just purchased. Then your update was free or discounted. You can also get a yearly renewal plan. It covers all major updates. In huge companies this is sometimes faster and easier than updating at release time.

Markus

ka_developer
Member
 

Joined: Tue Apr 20th, 2010
Location:  
Posts: 65
Status: 
Offline
Hello,

thank you for the quick reply.

We localize .sln of WPF application written in c#.

The idea is to build the solution so that we have all binaries and intermediate files created, then to delete the source files which are unnecessary for sisulizer. This reduced state can then be delivered to regional office where they will run sisulizer on .sln.

Could you please share the list of file types which are needed for localization and cannot be removed in this way? *.xaml, *.g.cs, *.cs, ...? (It shows errors if we remove .xaml)

Regards

Last edited on Fri Jan 18th, 2019 01:03 pm by ka_developer

Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3195
Status: 
Offline
To my knowledge you only need the visual studio project file plus binaries like exe and dlls.

I hope R&D will correct me if I`m wrong.
Markus

ka_developer
Member
 

Joined: Tue Apr 20th, 2010
Location:  
Posts: 65
Status: 
Offline
With our solution sisulizer says that .xaml files cannot be found if we delete them. We have no explicit references on them, only on .sln.

Regards

Last edited on Fri Jan 18th, 2019 02:35 pm by ka_developer

Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 2011
Status: 
Offline
For WPF projects you need .csproj/.vbproj and all .XAML files and all .resx file. No source code file (.cs/.vb) is needed.

For Windows Forms you you also need full source code files.

Ilkka



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

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize