|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Runtime Language Change for sisulizer - Wish list for software localization tool - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
MagicFX Member
|
I was wondering why sisulizer can't change language in runtime? (As the screenshot) What's the difficulty in implementaion? Not easy enough for non-.Net framework? Is that resource consuming? Can you provide a .NET (C#) and a C++ sample projects that support multilanguage but do NOT change language in runtime? I wanna compare the codes, thank you! Attachment: sisulizer_langugae_change.png (Downloaded 20 times)
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
MagicFX Member
|
here is the eng interface screenshot Attachment: sisulizer_langugae_change_en.png (Downloaded 20 times)
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Currently there is quite a lot dynamic creation (e.g. UI items that are created at run time) in Sisulizer. This is why we do not have runtime languages switch. However we will implement runtime language switch in the next major Sisulizer version. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
MagicFX Member
|
So would you please add two new C# sample projects that both create some dynamic UI in the latter sisulizer version: One project supports runtime language change but the other doesn't. Thank you.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
There are two kind of UI items on a component based development tools (e.g. Delphi and .NET): 1) First one are the static ones. They are the components (labels, menus, etc) that you add on the form desinger of your IDE. These components get stored on the form resource file (.resx or .dfm) 2) Second are the dynamic ones. They are components that are created on run time use Pascal, C# or VB code. They are not stored on the form resources. In moset cases you use string resources to assing a value to the component's property after creating it. Sisulizer's runtime languages code automatially translates all static controls. You just have to call function that ask a new language from user and performs language change. However in order to translate the dynamic ones to the new target language you have to write your own code. The logic is like this (in Delphi) if SelectResourceLanguage('EN') then begin TranslateDynamicPart; end; Here SelectResourceLanguage is Sisulizer's rutime language change code, TranslateDynamicPart is function that you wrote and it reassings the properties of the dynamic controls procedure TranslateDynamicPart; begin myDynamicLabel.Caption := SCaptionText; end; Here SCaptionText is a resource string. After language change its values has been changed to new language and the above code assings it to label's Caption property. I will write sample applications for C# and Delphi that demonstrated this. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 12:17 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) > Wish list for software localization tool > Runtime Language Change for sisulizer | |
Sisulizer software localization tool - Three simple steps to localize
