|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Warning when resource DLL becomes incompatible
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Warning when resource DLL becomes incompatible
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Warning when resource DLL becomes incompatible - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Maarten Member
|
When a version of our software is (almost) ready for delivery, we send the English resource DLL's to an external translation service, to have them translated to other languages. In our software build process, we would like to be triggered when the software becomes incompatible with the resource DLL's we have sent to the translation service. We can then send the new English resource DLL's to the tanslation service, so that they can translate the differences and incorporate them in the foreign language resource DLL's. Has Sisulizer got features built-in to give us such a trigger (for example by comparing two versions of the same English resource DLL)? Regards, Maarten.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Maarten, with Sisulizer you would not have this incompatibility problems. You would simply create a Sisulizer project and add your resource dll to it. Then you would send the extracted strings - and not the dll - to your translation service. If the strings come back translated you can use them to build the translated dll. If you dll changes you simply use "Project - Scan for Changes". Sisulizer finds all changes in your dll and only changed or new strings need to be translated. You can make Sisulizer part of the make run of your software with its command line tool. This way you always have an up-to-date dll and never incompatibilities. Advantages at a glance: - your dll always matches the build of your software. The problems of incompatible dlls go away - you translation service can concentrate on translating strings - Sisulizer finds changed and new strings with new builds and re-uses unchanged strings automatically. - it is only a minor change to the way you work now. Instead of sending the whole dll you send only the strings With a little change to your process you will not need any trigger. Best Markus Last edited on Fri Sep 7th, 2007 04:11 pm by Markus.Kreisel ____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:37 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Warning when resource DLL becomes incompatible | |
Sisulizer software localization tool - Three simple steps to localize
