This is a migrated thread and some comments may be shown as answers.

Changing RadEditor spell check dictionary on server

0 Answers 123 Views
Editor
This is a migrated thread and some comments may be shown as answers.
George
Top achievements
Rank 1
George asked on 06 Oct 2011, 02:16 PM
Hello,

I am trying to change the RadEditor Spell Check Dictionary Path on the server (Page Load), but I am unable to get it to work. Here is what I have:

RadEditor1.SpellCheckSettings.DictionaryPath = "/include/RadControls/Spell/TDF"
If Threading.Thread.CurrentThread.CurrentCulture.Name.ToLower() = "es-pr" Then
    RadEditor1.SpellCheckSettings.DictionaryLanguage = "es-ES"
    RadEditor1.SpellCheckSettings.SpellCheckProvider = Telerik.Web.UI.SpellCheckProvider.EditDistanceProvider
Else
    RadEditor1.SpellCheckSettings.DictionaryLanguage = "es-US"
    RadEditor1.SpellCheckSettings.SpellCheckProvider = Telerik.Web.UI.SpellCheckProvider.PhoneticProvider
End If

I have to set those values on the server because we have spanish users, so we need to change the dictionary language and provider for those users. When I click on the spell check button on the RadEditor, i just get a server error 500 - Dictionary Path is not set. I have attached a picture of the error.

However, I do not get this error when I add the dictionary path to the client:

<telerik:RadEditor ID="RadEditor1" runat="server" SpellCheckSettings-DictionaryPath="/include/RadControls/Spell/TDF">
    <Content>
    </Content>
</telerik:RadEditor>

This would work fine, but I'm afraid the provider and dictionary language still would not be set.

Is there anyway for these values to be set on the server side? Thanks for your help!



EDIT:

I have found that the DictionaryPath works correctly if I take out the DictionaryLanguage.  For some reason RadEditor1.SpellCheckSettings.DictionaryLanguage = "es-US" is causing the DictionaryPath to be blank when running the spell check.


EDIT 2:

OK. Disregard my stupidity. I actually noticed my error while reading the last edit. The "es-US" should be "en-US". After changing that, it works as it should.

No answers yet. Maybe you can help?

Tags
Editor
Asked by
George
Top achievements
Rank 1
Share this question
or