|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Cannot run translated application from Translation Edition
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Cannot run translated application from Translation Edition - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
lybra Member
|
We have created a Sisulizer Translation Edition by choosing File > Exchange. The translator installs it on his machine and the project opens. He can start translating, but choosing Project > Run Original will not result into anything, and Project > Run Localized never becomes activated at all. We would very much like for the translator to run the translated application, so he can see the result of his work. How can we do this? We are using 1.6.3. edit: I seem to have misplaced this topic. Could an administrator please move this topic to the correct forum? Last edited on Tue Aug 21st, 2007 06:20 pm by lybra |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Lybra, the free translator edition can only be used to translate. It can not be used to create new projects (scan) or create the output (build). If you want your translator to have the build option you need to get an own full license from him/her. We have very nice priced multi-volume packages: http://www.sisulizer.com/buy-information.shtml#price The menu item you named should perhaps be better disabled in the free translator edition. While your origianal exe is not part of the exchange package it can not be found on your translators machine. Therefore it can not be started. I will discuss with our developers if we can make this a bit clearer in future builds with some warning or disabling of that menu item. Hope this helps. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
lybra Member
|
Thanks for the explanation. Obviously this will work, however giving the translator a full license might give him a bit too many options. Thanks again, André.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
lybra wrote: translating, but choosing Project > Run Original will not result into anything, and Project > Run Localized never becomes activated at all. Project | Run Original is enabled only if the translator's computer contains the original file. By default Sisulizer includes only the project file (.slp) to the exchange package and this is why translator does not have the file. If changed in 1.6.4 that Project | Run Localized (and the corresponding button) are hidden in Translators Edition. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
lybra Member
|
_(at)_Jaakko:Project | Run Original is enabled only if the translator's computer contains the original file. I don't know exactly what you mean with "original file", but what we did was create a sample C# application on machine 1, create a Sisulizer Translation Edition for this application on machine 1 using File > Exchange and the default settings, and send the output of this (an executable that includes the Sisulizer installer) to machine 2. On machine 2, the Project > Run Original option is enabled (and does nothing). The same goes if I don't use File > Exchange to create an installer on machine 1, but simply send the .slp file created on machine 1 to machine 2: on machine 2, the Project > Run Original option is enabled. The C# application is not present on machine 2 (no C# source files, no executable).
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
Original file is the file that is being localized. In C# case it is either assembly file (.exe or .dll) created by the compiler or the actual Visual Studio project file (.csproj). Did you added .exe or .csproj to Sisulizer project? I did not know you file type (C#) so I tested other file types. I will test C# project file (.csproj). Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
lybra Member
|
Yes, we used the .csproj file to create the Sisulizer project on machine 1. Machine 2 does not have the .csproj. Thanks for your efforts, André.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
I fixed this in 1.6.4 Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
lybra Member
|
Excellent! Can you tell me when 1.6.4 will be released? Thanks, André.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
Tomorrow
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
lybra Member
|
Jaakko, I have tested with 1.6.4 and the Run original option in the Translator edition is indeed disabled now. Thanks, André.
|
|||||||||||||
| ||||||||||||||
| Current time is 11:52 pm | |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Cannot run translated application from Translation Edition | |
Sisulizer software localization tool - Three simple steps to localize
