|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Best Strategy for Large Projects - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
renatonow Member 
|
Hi: The company I am involved with has a suite of applications composed of several large libraries such as Static Libraries (.lib), Dynamic Libraries (.dll) as well as COM components. Each of them has their own set of resources. Those libraries are reused among several applications: executable files (.exe) that mix the libraries together. The application itself also has its own set of resources. It would be nice to reuse as much translation work as possible. What would be the best strategy in this scenario? Is there any need to modify or structure the project in a particular way to enable a frictionless tranlation job? Regards, Renato
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Renato, if you add all projects to Sisulizer it can make use of it's build in automatic translation reuse. Whenever it sees a string already translated it aks you if you want to reuse it for the other occurences. If you want to split the project into pieces (more than one .slp), then you should store your translations also in a the translation memory. This way you can reuse translations in several independed .slp files. While you seem to be new to Sisulizer I do not want to forget to mention, that if you make an upgrade of your software and you rescan to reflect the changes Sisulizer automatically reuses existing translations. And of course you also can import existing translations from already translated binaries (by value and/or by reference). To make it perfect there is also an TMX import/export to exchange translations with your translator. You see, there are many ways to avoid double translations in Sisulizer! Hope this help Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 04:52 am | |
| 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 > Best Strategy for Large Projects | |
Sisulizer software localization tool - Three simple steps to localize
