This question is locked. New answers and comments are not allowed.
Michel Salib
Top achievements
Rank 1
Rank 1
Michel Salib
asked on 09 Aug 2010, 03:12 PM
Hi.
I'am developing a web application with all my localization labels into a database. Thus, I created a Custom Tool for my resources files (*.resx) that will seek for the translation into my database.
I also wanted to have the telerik grid to use this logic. I copied the GridLocalization.en-US.resx provided with the telerik pakage and copid it into my App_GlobalResources folder. I renamed it to GridLocalization.resx so that it will be used with any current culture of my application. Then I register the script into my webpage :
Until this point the use of the resx file goes perfectly well. When I change a label into the resx file it also changes on the grid.
But, when I wanted to use my custom tool with the resources file, it didn't work. I discovered that Telerik does not access the localization label via the commun accessors and thus my custom tool is completly bypassed.
I am doing something wrong ? Is their any workaround or any future development of telerik that will solve this issue ?
I'am developing a web application with all my localization labels into a database. Thus, I created a Custom Tool for my resources files (*.resx) that will seek for the translation into my database.
I also wanted to have the telerik grid to use this logic. I copied the GridLocalization.en-US.resx provided with the telerik pakage and copid it into my App_GlobalResources folder. I renamed it to GridLocalization.resx so that it will be used with any current culture of my application. Then I register the script into my webpage :
Html.Telerik().ScriptRegistrar().Globalization(true)Until this point the use of the resx file goes perfectly well. When I change a label into the resx file it also changes on the grid.
But, when I wanted to use my custom tool with the resources file, it didn't work. I discovered that Telerik does not access the localization label via the commun accessors and thus my custom tool is completly bypassed.
I am doing something wrong ? Is their any workaround or any future development of telerik that will solve this issue ?