I am trying to implement the Editor, and is using a simple ToolsFile.xml. I wish to run the editor in default language (English) and with no spell checker.
However, none of the buttons/interface texts in the Editor has any translations? I have not copied anything to App_GlobalResources, because as far as your examples state, the standard languages are included in the DLL. Still, all the texts only have the default name values, like FindAndReplace etc., and the especially dialogue windows are completely unusable/unreadable.
What am I doing wrong?
It should be noted that I'm running a custom database localization for the rest of the site - is this interfering with RadEditor?
However, none of the buttons/interface texts in the Editor has any translations? I have not copied anything to App_GlobalResources, because as far as your examples state, the standard languages are included in the DLL. Still, all the texts only have the default name values, like FindAndReplace etc., and the especially dialogue windows are completely unusable/unreadable.
What am I doing wrong?
It should be noted that I'm running a custom database localization for the rest of the site - is this interfering with RadEditor?
3 Answers, 1 is accepted
0
EET Group
Top achievements
Rank 2
Rank 2
answered on 15 Dec 2008, 01:17 PM
Well, I found the problem. My custom localization returns the Key text for translations that does not exist. Changing it to return null gave me default translations in the Editor.
I think you should note though, that I apparently cannot use .resx files together with my custom resource provider. Could you think of a way around this? I find it suboptimal to have to throw all your .resx files into my DB.
I think you should note though, that I apparently cannot use .resx files together with my custom resource provider. Could you think of a way around this? I find it suboptimal to have to throw all your .resx files into my DB.
0
Hi,
I think the problem in your case is that all the strings from the resource files are also available as localizable properties in the RadEditor control. For example:
RadEditor1.Localization.Main.AddCustomColor = "Add Custom Color";
Your localization provider picks up the "Localizable" attribute of these properties and sets their values, overriding the built-in resource files or the ones from App_GlobalResources. Setting the properties to null will allow the normal editor localization (using built in resources or .resx files) to take over.
All the best,
Lini
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
I think the problem in your case is that all the strings from the resource files are also available as localizable properties in the RadEditor control. For example:
RadEditor1.Localization.Main.AddCustomColor = "Add Custom Color";
Your localization provider picks up the "Localizable" attribute of these properties and sets their values, overriding the built-in resource files or the ones from App_GlobalResources. Setting the properties to null will allow the normal editor localization (using built in resources or .resx files) to take over.
All the best,
Lini
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
EET Group
Top achievements
Rank 2
Rank 2
answered on 16 Dec 2008, 11:33 AM
Yes you are right. This is more of a problem with my custom resource provider. I have worked around it. Thanks.