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
BuildError - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Wed Feb 21st, 2018 04:19 pm
PM Private Upload Quote Reply
Daniel Wassenegger
Member
 

Joined: Wed Feb 21st, 2018
Location:  
Posts: 4
Status: 
Offline
Hello,

I hope this post will work (third try; twince internal error on this page!)

We get the Sisulizer Pro one week ago and try now to finalize the translation of a new project for France!

Problem: One of the 6 files were not translated. (Build Error)
The BaseTypes.dll did not work. (GCOWebAccess.dll, GCOMain.exe, HealthMonitoringProcess.exe - have no problems)
The error is: "Konnte die ResourceDIctionary.fr.xaml-Datei nicht kompilieren. The same error comes then for "SlimTabControlTemplate", too.


I have read ond entries at this forum but the only solution I get (or understand) is, that I have to take the VStudio Project or Sultion, but this is no option; because I do not have it!

Our development department, sends the files for translation to me and I translate it and send it back. Some files (like Dlls), I just need to copy into our resource-folder and restart application or change language, then the program will use them automatically.
I get no access to the source-code or the project-files!


Best Regards

Daniel W.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Feb 21st, 2018 04:53 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

Possibilities:

To localize a .NET project you need to have the binaries plus the project file (not the source code). The project file has info how to build the binaries not stored in the binaries. You could send your translations to a person that has the project file and he builds the binaries with his license. This is no limitation of Sisulizer. All localization tools need a few infos from the project file for a succesfull build run. In the beginning our R&D tried to implement a pure binary localization. Ths experimental code is still in Sisulizer for compability reasons. It might work in a few cases. But some information simply can`t be found in the binaries alone. If this occors there us nothing that can be fixed except getting the info from the project file.

As an alternative you can localize the resx files instead of the binaries. You would then send the translated resource files to the developers who can build the localized binaries with them.

The workflow for software localization is, that the developer of the software owns e.g. Sisulizer, creates a translation package, third party translates it and sends localization back. Developer builds the localized software.

Try to get the missing project file (no further source code) or the resx files.

I also asked R&D to look into your files. But I fear the missing info from the project file causes your issue.

Markus



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

 Posted: Wed Feb 21st, 2018 05:37 pm
PM Private Upload Quote Reply
Daniel Wassenegger
Member
 

Joined: Wed Feb 21st, 2018
Location:  
Posts: 4
Status: 
Offline
Hallo,

jetzt habe ich das Projekt dazu gebunden und bekomme folgende Fehlermeldungen:

19:33:31 Datei "C:\Translation Studio\Sisulizer Pro\gco\org\BaseTypes.csproj" durchsuchen
19:33:31 Fehler Datei "C:\Translation Studio\Sisulizer Pro\gco\org\CommonResources.xaml" existiert nicht.
19:33:31 Fehler Datei "C:\Translation Studio\Sisulizer Pro\gco\org\ErrorHandling\MainButtonsWnd.xaml" existiert nicht.
19:33:31 Fehler Datei "C:\Translation Studio\Sisulizer Pro\gco\org\ErrorHandling\MessageBarTemplates.xaml" existiert nicht.
19:33:31 Fehler Datei "C:\Translation Studio\Sisulizer Pro\gco\org\ErrorHandling\MessageBarWpf.xaml" existiert nicht.
19:33:31 Fehler Datei "C:\Translation Studio\Sisulizer Pro\gco\org\OverlayImageDetailOptionsControl.xaml" existiert nicht.
19:33:31 Fehler Datei "C:\Translation Studio\Sisulizer Pro\gco\org\WPF\AlphaTouchEditControlWpf.xaml" existiert nicht.
19:33:31 Fehler Datei "C:\Translation Studio\Sisulizer Pro\gco\org\WPF\NumericTouchEditControlWpf.xaml" existiert nicht.
19:33:31 Fehler Datei "C:\Translation Studio\Sisulizer Pro\gco\org\WPF\SlimTabControlTemplate.xaml" existiert nicht.
19:33:31 Fehler Datei "C:\Translation Studio\Sisulizer Pro\gco\org\WPF\WizardControls.xaml" existiert nicht.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Feb 21st, 2018 06:07 pm
PM Private Upload Quote Reply
Daniel Wassenegger
Member
 

Joined: Wed Feb 21st, 2018
Location:  
Posts: 4
Status: 
Offline
When I add the Project-File of BaseTypes.dll to the Sisulizer-Project; i get only more error messages (please refer last fast reply).

Maybe There is something special todo with the project file?

Back To Top PM Private Upload Quote Reply

 Posted: Wed Feb 28th, 2018 07:03 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 2006
Status: 
Offline
I looked your sample. Your application is a WPF application. I cannot be localized using just the binaries (.exe or .dll). You need to have the source code or at least .csproj, compiled assemblies, .resx and .XAML files.

Ilkka



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

 Posted: Thu Mar 1st, 2018 06:13 am
PM Private Upload Quote Reply
Daniel Wassenegger
Member
 

Joined: Wed Feb 21st, 2018
Location:  
Posts: 4
Status: 
Offline
Hello Ikka,

I already get csproj and XAML-Files.
I get no information what todo with this new files and just added them to the project. After it, I get a lot of further messages, that other files are missing!
----
But we needed a solution and so I switch off the XAML-Ressources option at the project and now it is working (but I think without some "at the moment not required" strings to translate!

Back To Top PM Private Upload Quote Reply

 Posted: Thu Mar 1st, 2018 08:30 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3140
Status: 
Offline
Dear Daniel,

He xaml files need to placed where the VS projects file expects them. In other words you need the same file structure as the complete project - but without source code in it. Sisulizer finds the files (binaries/resorces) from analyzing the project file.

Markus



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

Current time is 11:48 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > BuildError



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