|
|
Rank: Member
Groups: Member
Joined: 7/28/2008
Posts: 25
|
Thought I followed all the directions but I am getting this error: Dictionary file directory 'C:\Documents and Settings\MCTalbot\Desktop\NewEmailerShell\English\English' does not exist. Please check whether dictionary files have been correctly set up or the SpellChecker's Language property has been properly set. My web.config currently has this entry: <appSettings> <add key="eo_DictLocation" value="~/English"></add> </appSettings> Its also been tried with both the dir and web.config set to: <appSettings> <add key="eo_DictLocation" value="~/en-US"></add> </appSettings> Nothing I try seems to work. Please advise.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
I believe you set the directory eo_DictLocation to the parent directory of "en_US". You can open our sample project and check:
1. eo_DictLocation in web.config;
2. Files in eo_dict directory;
Try to duplicate that structure in your app and it should get you going.
Hope this helps.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 7/28/2008
Posts: 25
|
Dictionary file directory 'C:\Documents and Settings\MCTalbot\Desktop\NewEmailerShell\eo_dict\en_US' does not exist. Please check whether dictionary files have been correctly set up or the SpellChecker's Language property has been properly set Not sure I'm tracking with you Heres a snapshot of my project: http://www.linkedtechnology.com/mysolutionsexplorer.bmpAlso, my web.config entry is now set to: <appSettings> <add key="eo_DictLocation" value="~/eo_dict"></add> </appSettings>
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi Mike,
Can you just follow our previous reply? I believe it has already provided clear instructions on what to do.
Thanks
|
|
Rank: Member
Groups: Member
Joined: 7/28/2008
Posts: 25
|
I finally figured it out on my own and it wasnt clear to me was that I needed a sub-directory (en_US) , and two dic files (.dic and .aff) in that sub directory.
If this was clearly outlined in your guidelines, then I apologize for my stupidity which you seem to be pointing out in your last reply.
Sorry - your last reply simply confused me and didnt include all the instructions I needed to get this working.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi, The directory structure is clearly outlined in the guideline: http://www.essentialobjects.com/ViewDoc.aspx?t=SpellChecker%2fstart.htmlCheck the #3 in "Setting up dictionary files" section. Our last reply point you to our sample projects and told you to "duplicate that structure". If you take a look of the sample project source code on your local harddrive, you will see the same directory structure. You can just copy everything from there to your project. We thought that would be the easiest way for you see how it supposes to be, that's why we ask you to follow that instead of just keep staring at your own project structure. Thanks
|
|
Rank: Member
Groups: Member
Joined: 7/28/2008
Posts: 25
|
You have successfully now made me feel even more worng. Great job!
I am sure you feel very satifsfied now that you have gone out of your way to expose more of my short-comings. I wasnt attacking your product, simply looking to be pointed in the right direction.
You have the benefit of knowing this stuff backwards and forwards. I however, read your documentation, attempted to use your control and I failed. All I was looking for was some guidance, and not to be made an to feel like I took advantage. Obviously, your contiued replies are designed to show everyone else who might read this Forum how smart you are about your own product. Your approach to support needs a bit of work in my somewhat "challenged" opinion.
A simple, "Glad you were able to get the control working" or "is there anything we can do to make this more clear to other users?" would have been great.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
It's not about whether we are smart or not. It was a simple question, we gave you a simple answer. You would insist we confused you. We would insist that we did what we thought was the best for you. Unfortunately sometimes you and us are not on the same page. It does happen and when that happens, we tell you our reasons. It's all technical. While we can understand that you may feel offended, but it is totally unnecessary. We are of course glad that you were able to get it working. After all that's what matters most.
|
|