15 Answers, 1 is accepted
0
Hi Ricky,
The localization of the RadWindow control is done with an XML file which can be found in your RadControls/Window/Localization/<your localization> folder. More information on the subject is available in the RadWindow documentation, section Customizing Behavior / Localization.
Regards,
Georgi Tunev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
The localization of the RadWindow control is done with an XML file which can be found in your RadControls/Window/Localization/<your localization> folder. More information on the subject is available in the RadWindow documentation, section Customizing Behavior / Localization.
Regards,
Georgi Tunev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Ricky
Top achievements
Rank 1
Rank 1
answered on 23 Jan 2008, 12:47 AM
Hi,
under Prometheus Q3 root\Live Demos\RadControls, I could not find the Window folder you referred to; neither did I catch the sight of the document.
Reagrds,
Ricky.
under Prometheus Q3 root\Live Demos\RadControls, I could not find the Window folder you referred to; neither did I catch the sight of the document.
Reagrds,
Ricky.
0
Hi Ricky,
First of all I would like to apologize for my omission - I missed the fact that this thread is for the "Prometheus" version of the control and not the classic one - my reply was about the classic ASP.NET version of RadWindow.
As for the "Prometheus" version of the RadWindow control, we are currently considering to change the localization mechanism and to provide an easy and convenient way for localizing the control. We need some more time for research and implementation, and for now we can suggest to use the following workaround:
You can change the localization strings of the RadWindow "Prometheus" control by using the following Javascript code that should be placed after the RadWindow / RadWindowManager declaration:
Change the string after the colons and they will be shown in the tooltip when you hover over the RadWindow buttons.
Kind regards,
Georgi Tunev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
First of all I would like to apologize for my omission - I missed the fact that this thread is for the "Prometheus" version of the control and not the classic one - my reply was about the classic ASP.NET version of RadWindow.
As for the "Prometheus" version of the RadWindow control, we are currently considering to change the localization mechanism and to provide an easy and convenient way for localizing the control. We need some more time for research and implementation, and for now we can suggest to use the following workaround:
You can change the localization strings of the RadWindow "Prometheus" control by using the following Javascript code that should be placed after the RadWindow / RadWindowManager declaration:
| Telerik.Web.UI.RadWindowUtils.Localization = |
| { |
| "Close" : "Close", |
| "Minimize" : "Minimize", |
| "Maximize" : "Maximize", |
| "Reload" : "Reload", |
| "PinOn" : "Pin on", |
| "PinOff" : "Pin off", |
| "Restore" : "Restore", |
| "OK" : "OK", |
| "Cancel" : "Cancel", |
| "Yes" : "Yes", |
| "No" : "No" |
| }; |
Change the string after the colons and they will be shown in the tooltip when you hover over the RadWindow buttons.
Kind regards,
Georgi Tunev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Ricky
Top achievements
Rank 1
Rank 1
answered on 30 Jan 2008, 05:47 AM
Hi, Georgi
It seems that "PinOff" : "浮動視窗" does not apply to the changes; RadWindow still shows the localization string of "PinOn": "關閉視窗" on PinOff icon.
Regards,
Ricky.
It seems that "PinOff" : "浮動視窗" does not apply to the changes; RadWindow still shows the localization string of "PinOn": "關閉視窗" on PinOff icon.
Regards,
Ricky.
0
Hello Ricky,
I reproduced the problem locally and we recognize this as a bug on our side. I logged it in our database and we will fix it in one of the following updates.
Please accept our apologies for the temporary inconvenience. Your points were updated.
Best wishes,
Georgi Tunev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
I reproduced the problem locally and we recognize this as a bug on our side. I logged it in our database and we will fix it in one of the following updates.
Please accept our apologies for the temporary inconvenience. Your points were updated.
Best wishes,
Georgi Tunev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
mark
Top achievements
Rank 1
Rank 1
answered on 31 Jul 2008, 12:31 AM
Has this changed or the javascript workaround in this post is the only available way to localize radwindow?
0
Hi mark,
This is still a valid approach (with the Q2 release).
Sincerely yours,
Tervel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
This is still a valid approach (with the Q2 release).
Sincerely yours,
Tervel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Michael Ammer
Top achievements
Rank 1
Rank 1
answered on 08 Sep 2008, 08:02 AM
Hi!
I've got this thread from you for my question about the Language Property.
I'm not the specialist in using Javascript, so it would be fine from you, if you can provide a simple demo how to change the language from e.g. english to german.
btw: just for understanding: There is no Way to set the Language serverside, is it?
and: do you plan to implement this Feature again in further releases?
thx
p.s. I use telerik controls heavily all over my application and I can tell you, it is the pure pain to upgrade from 2007 to ASP.NET Ajax. Missing/renamed Functions, missing Properties and so on, Redo all the skins, changed paths...
Not really funny.
I've got this thread from you for my question about the Language Property.
I'm not the specialist in using Javascript, so it would be fine from you, if you can provide a simple demo how to change the language from e.g. english to german.
btw: just for understanding: There is no Way to set the Language serverside, is it?
and: do you plan to implement this Feature again in further releases?
thx
p.s. I use telerik controls heavily all over my application and I can tell you, it is the pure pain to upgrade from 2007 to ASP.NET Ajax. Missing/renamed Functions, missing Properties and so on, Redo all the skins, changed paths...
Not really funny.
0
Hello Michael,
Please find attached the requested sample. Currently this is the only way to localize RadWindow - we are considering to add support for changing the localization with a single property but this will happen on a later stage. If you want to change the localization based on some server-side event, you can output the JavaScript code in the same way as you would do with any other client code.
We are sorry to hear about the problems that you have encountered in the upgrading process but please note that RadControls for ASP.NET AJAX (Prometheus) is Telerik’s next-generation ASP.NET UI control suite, which is built on top of the industry-standard Microsoft ASP.NET AJAX framework.
We have fully re-architectured our controls to benefit from the latest AJAX capabilities and deliver faster performance, unified programming model and enhanced functionality. All our API conventions are now fully aligned with the ASP.NET AJAX APIs for a standardized and very easy developer experience. Also, all new controls are now shipped in a single assembly, which greatly simplifies the deployment. All resources (scripts, skins, etc) are also embedded in the assembly and if you use the built-in scripts/skins without any modifications you do not have to worry about any external files.
Last, but not least our framework and controls are now extended to support not only ASP.NET 2.0 but 3.5 as well and take full advantage of latest additions like LINQ, client-side features, WebServices, load-on-demand etc.
Due to all these changes RadControls for ASP.NET AJAX are not backwards compatible with RadControls for ASP.NET. (Please note that this is a new generation of controls not just another version). While for some products, the transition is going to be painless for other products, the migration will be more difficult due to the new architecture, use of single assembly, new API, and other changes introduced in RadControls for ASP.NET AJAX.
For every control we have a help topic dedicated to the upgrade from ASP.NET to ASP.NET AJAX version and the changes in the respective APIs. For example, this is the topic for RadGrid:
http://www.telerik.com/help/radcontrols/prometheus/?grdMigrationToPrometheus.html
We are always available to help you with any issues you have faced during the migration/upgrade process. Please do not hesitate to contact us and we will do our best to help you right away.
Greetings,
Georgi Tunev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Please find attached the requested sample. Currently this is the only way to localize RadWindow - we are considering to add support for changing the localization with a single property but this will happen on a later stage. If you want to change the localization based on some server-side event, you can output the JavaScript code in the same way as you would do with any other client code.
We are sorry to hear about the problems that you have encountered in the upgrading process but please note that RadControls for ASP.NET AJAX (Prometheus) is Telerik’s next-generation ASP.NET UI control suite, which is built on top of the industry-standard Microsoft ASP.NET AJAX framework.
We have fully re-architectured our controls to benefit from the latest AJAX capabilities and deliver faster performance, unified programming model and enhanced functionality. All our API conventions are now fully aligned with the ASP.NET AJAX APIs for a standardized and very easy developer experience. Also, all new controls are now shipped in a single assembly, which greatly simplifies the deployment. All resources (scripts, skins, etc) are also embedded in the assembly and if you use the built-in scripts/skins without any modifications you do not have to worry about any external files.
Last, but not least our framework and controls are now extended to support not only ASP.NET 2.0 but 3.5 as well and take full advantage of latest additions like LINQ, client-side features, WebServices, load-on-demand etc.
Due to all these changes RadControls for ASP.NET AJAX are not backwards compatible with RadControls for ASP.NET. (Please note that this is a new generation of controls not just another version). While for some products, the transition is going to be painless for other products, the migration will be more difficult due to the new architecture, use of single assembly, new API, and other changes introduced in RadControls for ASP.NET AJAX.
For every control we have a help topic dedicated to the upgrade from ASP.NET to ASP.NET AJAX version and the changes in the respective APIs. For example, this is the topic for RadGrid:
http://www.telerik.com/help/radcontrols/prometheus/?grdMigrationToPrometheus.html
We are always available to help you with any issues you have faced during the migration/upgrade process. Please do not hesitate to contact us and we will do our best to help you right away.
Greetings,
Georgi Tunev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Michael Ammer
Top achievements
Rank 1
Rank 1
answered on 09 Sep 2008, 08:25 AM
Thx for your fast response.
Meanwhile I found a solution for myself using the customised Windowtemplates. The tooltips are still in English - but this is no Problem.
Regarding to the rest: Of course I understand what problems a mayor relaunch of such a complex toolset means. And that's why I upgraded my application to the latest version. Help is (most time) fine too. but not in this special case. This Language property IS described in your help. No appearence in the changing list. No mention how to deal with localisation in special... well - this is a little confusing. ;)
Well. Case closed from my side. My windows are shown in best german / english or however using resourcefiles.
Thank you again for your help.
greetings from Austria
Michael
Meanwhile I found a solution for myself using the customised Windowtemplates. The tooltips are still in English - but this is no Problem.
Regarding to the rest: Of course I understand what problems a mayor relaunch of such a complex toolset means. And that's why I upgraded my application to the latest version. Help is (most time) fine too. but not in this special case. This Language property IS described in your help. No appearence in the changing list. No mention how to deal with localisation in special... well - this is a little confusing. ;)
Well. Case closed from my side. My windows are shown in best german / english or however using resourcefiles.
Thank you again for your help.
greetings from Austria
Michael
0
Syed Furqan
Top achievements
Rank 1
Rank 1
answered on 23 Mar 2009, 03:01 PM
Hello,
I am localizing the rad window but I have check for Japanese etc culture. So I cannot simply put
I tried with
Dim radWindowLocalizationScript As String = String.Format("Telerik.Web.UI.RadWindowUtils.Localization = " & _
"{{ " & _
"Close : {0} ," & _
"Minimize : {1}, " & _
"Maximize : {2}, " & _
"Reload : {3}, " & _
"PinOn : {4}, " & _
"PinOff : {5}, " & _
"Restore : {6}, " & _
"OK : {7}, " & _
"Cancel: {8}, " & _
"Yes : {9}, " & _
"No : {10} " & _
"}}; ", _
arrayOfObjects)
myPlaceHolder is just after the RadWindow declaration
and
2. 'RadScriptManager.RegisterStartupScript(Me.Page, Me.GetType, "_radWindowLocalizationScript", radWindowLocalizationScript, True)
but could not succeed. Basically these these {0},{1} etc will be manipulated after checking the culture.
Is there any option ?
I am localizing the rad window but I have check for Japanese etc culture. So I cannot simply put
Telerik.Web.UI.RadWindowUtils.Localization = |
| { |
| "Close" : "Close", |
| "Minimize" : "Minimize", |
| "Maximize" : "Maximize", |
| "Reload" : "Reload", |
| "PinOn" : "Pin on", |
| "PinOff" : "Pin off", |
| "Restore" : "Restore", |
| "OK" : "OK", |
| "Cancel" : "Cancel", |
| "Yes" : "Yes", |
| "No" : "No" |
| }; |
I tried with
Dim radWindowLocalizationScript As String = String.Format("Telerik.Web.UI.RadWindowUtils.Localization = " & _
"{{ " & _
"Close : {0} ," & _
"Minimize : {1}, " & _
"Maximize : {2}, " & _
"Reload : {3}, " & _
"PinOn : {4}, " & _
"PinOff : {5}, " & _
"Restore : {6}, " & _
"OK : {7}, " & _
"Cancel: {8}, " & _
"Yes : {9}, " & _
"No : {10} " & _
"}}; ", _
arrayOfObjects)
- myPlaceHolder.Controls.Add(New LiteralControl())
myPlaceHolder is just after the RadWindow declaration
and
2. 'RadScriptManager.RegisterStartupScript(Me.Page, Me.GetType, "_radWindowLocalizationScript", radWindowLocalizationScript, True)
but could not succeed. Basically these these {0},{1} etc will be manipulated after checking the culture.
Is there any option ?
0
Syed Furqan
Top achievements
Rank 1
Rank 1
answered on 25 Mar 2009, 12:59 PM
I found the solution .. I was missing quotes.
Furqan
Furqan
0
Hello Furqan,
You need to make sure that the localization strings are enclosed in quotes for this approach to work. For demonstration purposes I attached a small sample where I localize only the first 3 strings for RadWindow in Page_Load. I hope this helps.
Sincerely yours,
Georgi Tunev
the Telerik team
Check out Telerik Trainer , the state of the art learning tool for Telerik products.
You need to make sure that the localization strings are enclosed in quotes for this approach to work. For demonstration purposes I attached a small sample where I localize only the first 3 strings for RadWindow in Page_Load. I hope this helps.
Sincerely yours,
Georgi Tunev
the Telerik team
Check out Telerik Trainer , the state of the art learning tool for Telerik products.
0
Andrea
Top achievements
Rank 2
Iron
Rank 2
Iron
answered on 19 May 2009, 03:23 PM
Idea!
A common localization system to all your controls?
Best regards
A common localization system to all your controls?
Best regards
0
Hello Andrea,
Thank you for the suggestion - we are already using global resource files for localizing some of our controls and we are planning to extend this functionality to cover the rest of the controls like RadWindow or to provide another easy way for localization.
All the best,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Thank you for the suggestion - we are already using global resource files for localizing some of our controls and we are planning to extend this functionality to cover the rest of the controls like RadWindow or to provide another easy way for localization.
All the best,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.