Hello.
I see from an old post (http://www.telerik.com/community/forums/thread/b311D-tateh.aspx) that it was stated the Telerik doesn't plan to add localization support to the toolbar.
Does that still hold for the new Prometheus controls? We are in the process of upgrading to the new version of the controls and we're also adding localization support at the same time. Do we have to create separate content files for each language and switch on the fly to achieve this, or is there now some built in support for localization?
If there is no built in support, are there some good examples of switching the content files on the fly out there?
Thanks!
I see from an old post (http://www.telerik.com/community/forums/thread/b311D-tateh.aspx) that it was stated the Telerik doesn't plan to add localization support to the toolbar.
Does that still hold for the new Prometheus controls? We are in the process of upgrading to the new version of the controls and we're also adding localization support at the same time. Do we have to create separate content files for each language and switch on the fly to achieve this, or is there now some built in support for localization?
If there is no built in support, are there some good examples of switching the content files on the fly out there?
Thanks!
6 Answers, 1 is accepted
0
Hi akohlbeck,
We decided to stick to the default localization mechanism provided by ASP.NET 2.0: in Visual Studio design time you can choose Tools -> Generate Local Resource and you'll have an XML file generated, where you can set the Text and ToolTip properties for the RadToolBar items.
I hope this helps.
Kind regards,
Erjan Gavalji
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
We decided to stick to the default localization mechanism provided by ASP.NET 2.0: in Visual Studio design time you can choose Tools -> Generate Local Resource and you'll have an XML file generated, where you can set the Text and ToolTip properties for the RadToolBar items.
I hope this helps.
Kind regards,
Erjan Gavalji
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
tjans
Top achievements
Rank 1
Rank 1
answered on 20 May 2008, 01:40 PM
Is there anything extra that you have to do to tie the Prometheus controls to the resource file generated from Visual Studio? It doesn't seem to be replacing the text...
We are in a DotNetNuke project, I know for DNN localization of standard ASP labels, you have to specify the "resourcekey" attribute to get localization to work. Is there something similar for the Prometheus controls?
We are in a DotNetNuke project, I know for DNN localization of standard ASP labels, you have to specify the "resourcekey" attribute to get localization to work. Is there something similar for the Prometheus controls?
0
Hi travis.jansen,
Indeed, the meta:resourcekey attribute is the one, used by the ASP.NET localization to replace the localized property values. Please, find attached a simple page, demonstrating the local resource file usage.
Kind regards,
Erjan Gavalji
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Indeed, the meta:resourcekey attribute is the one, used by the ASP.NET localization to replace the localized property values. Please, find attached a simple page, demonstrating the local resource file usage.
Kind regards,
Erjan Gavalji
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
tjans
Top achievements
Rank 1
Rank 1
answered on 20 May 2008, 03:21 PM
Thank you for your quick response. Your example did work out of the box, but we are unable to specify which resource file to use based on the locale. No matter what locale is set for the user, your example still pulls the text from Default.aspx.resx. That's problem number one, and frankly the most important one.
Also, in our project, we are getting some strange behavior. I had an existing toolbar on my user control, and the project built and ran fine (althought it didn't localize). I then copied the code from the example you provided into my user control, and it gave me the error stating that I would need an axd http handler. I was able to get that in my web.config, but I wonder why your toolbar would need that and my existing one did not. After all that, the copied in code is still not localizing text.
Question two is why does the toolbar require a scriptmanager and an http handler?
Also, in our project, we are getting some strange behavior. I had an existing toolbar on my user control, and the project built and ran fine (althought it didn't localize). I then copied the code from the example you provided into my user control, and it gave me the error stating that I would need an axd http handler. I was able to get that in my web.config, but I wonder why your toolbar would need that and my existing one did not. After all that, the copied in code is still not localizing text.
Question two is why does the toolbar require a scriptmanager and an http handler?
0
tjans
Top achievements
Rank 1
Rank 1
answered on 20 May 2008, 04:45 PM
After some more testing, I was able to get your code to work switching the different locales, but I am not able to get it to work in a DNN module. Has the localization been confirmed to work in DNN modules?
0
Hello travis.jansen,
I think you would find the following forum thread helpful:
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/111/threadid/217612/scope/posts/Default.aspx
Regards,
Albert
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
I think you would find the following forum thread helpful:
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/111/threadid/217612/scope/posts/Default.aspx
Regards,
Albert
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center