|
|||
|
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 > Let an external translator build and try .Net satellite assemblies
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Let an external translator build and try .Net satellite assemblies - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
cgrill75 Member
|
I am currently evaluating Sisulizer for translating our applications that are targeted for Windows CE and .Net Compact Framework. On my development machine, I can easily generate the satellite assemblies after translation from within Sisulizer when starting a translation based upon the Visual Studio Solution file. However, if I export the project for external translation, this feature seems to be missing when I open the translation package on a different machine? Am I missing something? How can I give an external translator the comfort of translating and compililing the satellite assemblies without having to give away the complete source code or force the translator to install Visual Studio? The deployment of the assemblies to the device is a rather simple task that I can accomplish using a simple batch, if required.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi cgrill75, the Sisulizer Free edition can only translate, but neither scan nor build. This is by design. The regular way for your translator is to send back the translated stings to you and you build the binaries with your license. But since V2008 we have a new edition for advanced translators: Translator Edition. With this edition your translator can do everything except creating new projects. See a description of the editions: http://www.sisulizer.com/sisulizer-features.shtml If you give you translator the needed assemblies he can use the Translator Edition to build localized copies of them without seeing any source code. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
cgrill75 Member
|
Thanks for the quick response. However, obviously, the exchanged wizard can't be used for that?! I tried to open the output of the wizard (the .slp-File) in an evaluation version that I started as translator edition but still didn't get the functionality. How do I have to export in that case?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, you export with the exchange wizward, but you do not need to include the Free edition. Sinply use the option "Project file". You will get a .sle file you send your translator. He downloads and installs Sisulizer fro our download page: http://www.sisulizer.com/downloads.shtml. Before he starts work he enters his license key for the Translator Edition to get the needed features and remove the eval strings in the output. If he gets the .sle from you the Translator Edition will make a copy of it with the .slp extention. He then works on this .slp. Markus Attachment: 0059.JPG (Downloaded 9 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 10:24 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 > Let an external translator build and try .Net satellite assemblies | |
Sisulizer software localization tool - Three simple steps to localize
