Hi, first let me tell you that you guys are at ITG doing an extraordinary job. This looks like our way out of the VWG soap opera that we have been dragged to. Now, this may be a dumb question but I just don’t find how to work it out. I can get some labels translated to spanish when I set the culture value in the default.json file, but this does not change the labels in the dialog boxes (like the message box with yes/no options). Is this localization wating for latter or am I missing something? Thanks!
Regards,
Abelardo Cecena
Hi Abelardo,
you can make use of the system message localization with our latest build (1.2.76).
Please take a look at the updated Localization sample in our examples section to see how to configure additional translations.
Thanks and best regards
Frank
Hi Frank,
I tested it and yes, system messages localization is now working in 1.2.76. Thank you very much!
Regards,
Abelardo Cecena
Hi Luca, thank you for your answer. Yes, in fact I was asking about those systems labels localization. It’s great to know that they will be included in a future release. Thanks again for the great work!
Regards,
Abelardo Cecena
Hi Abelardo,
Looks like I misunderstood your question. You were asking about localizing the system’s message box and I answered something else. ?
As of now we have localized the system strings only to German. However, Wisej supports the custom localization of system labels as well, except that the message box button labels haven’t made it out of the TODO list. I will make sure they are included in the next update. To localize the system labels, simply add the localized strings using these IDs:
MonthCalendar control:
“$Next year”
“$Next month”
“$Last year”
“$Last month”
MessageBox, not recognized yet, but you can add them and they will work with the next update.
“$OK”
“$Yes”
“$No”
“$Cancel”
“$Retry”
“$Abort”
“$Ignore”
Best,
Luca
Hi Abelardo,
Thank you for your kind words.
Wisej uses the standard localization resources in .NET. You can store your own resources for strings or any other object, and you can use the localization tool at design time.
At design time, on a form, set Localizable to true, then select the current culture in the Language property and change the labels in the form. You can localize more than just the labels, you can set the size, location, change images, etc. In addition to Visual Studio built-in localization, you can use any third party tool to manage the localization resources, my favorite is ResXManager.
Take a look at the localization example here: https://wisej.com/examples/
NOTE: Consider that if you are using the designer to localize the labels, the localized labels are loaded only once when the form is created since the labels are loaded in InitializeComponent() which is called by the constructor. To test the localization you have to create a new session. You can force a new session adding ?sid=new to the URL. You can also change the language by adding lang={language} to the URL, i.e. /?lang=fr.
Best,
Luca
