|
|||
|
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 practice for .Net 2.0 C# project: binary- or resx-based localization?
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Best practice for .Net 2.0 C# project: binary- or resx-based localization? - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Tobias Member
|
Hi, we're starting to translate a C# .Net 2005 project solution using Sisulizer. Are there any advantages using resx-based localization vs. binary localization? We plan to use the professional or translation suite for translation and use an Enterprise version on a dedicated build server that produces automated builds with NAnt. Any help is appreciated. Thanks in advance, Tobias
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Tobias, binary localization is the recommended way you should use. It is easier and faster to use. You do not need to recompile your application if you add languages or change translations. it is simply the most modern way to do software localization. If you want to purchase multiple licenses you should take a look at our multi-volume price sheet: http://www.sisulizer.com/buy-information.shtml#price Until 31.10 two Enterprice lics cost only 2082 EUR while the sum for a Pro plus an Enterprise is 2240 EUR! Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Tobias Member
|
Hi Markus, thanks for the quick reply. Recompilation is not a problem as we have checked in the Sisulizer project file as well as the resx files and checking in results in a new automated build anyway. So despite of this there are no differences between the two approaches? Things we can do / can't if we choose one of the approaches, for example concerning (licensed) third party components or using automated translation with the slmake command line tool ? Kind regards, Tobias
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Hi Tobias, If you are a developer and you have full source code of the project (e.g. .csproj, .cs, .resx, etc) the recommended way is the project file localization. This means that you select the .csproj or .sln file. It is faster than binary localization, it is the method we mostly use at Sisulizer, and in addition it gives you localized .resx files. Even you don't really need localized .resx file (they are only intermediate files on the way to localized satellite assembly files) some developer feel more comfortable having them. No matter what method you select (EXE or project file) the result is the same: localized satellite assembly files. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi, Markus was right that binary localization is the preferred localization method in WIN32. However in .NET currently we prefer project file localization over binary localization. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Tobias Member
|
Hi Jaakko, Markus, thanks for your replies. I'm gonna give the project file localization a try  Best, Tobias
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Tobias, yes, in the end both methods are similar good in Sisulizer and it is up to you which one you prefer. We support you with both and of course you can later easily switch without loosing translations :-) Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 02:55 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 practice for .Net 2.0 C# project: binary- or resx-based localization? | |
Sisulizer software localization tool - Three simple steps to localize
