My Account |  Site Map | Contact Us  
Welcome Guest Search | Active Topics | Sign In | Register

SpellChecker dictionary Options
Posted: Wednesday, June 5, 2019 5:03:26 AM
Rank: Newbie
Groups: Member

Joined: 6/5/2019
Posts: 1
Hi @all

we have integrated the EO.WebBrowser in our system and uses spell checking but have issues with that.

As our users will need a highly specialized vocabulary, we would like to provide them with an appropriate dictionary to prevent forcing each user to train the system individually.
Is it possible to use own dictionaries for this or merge them with existing ones?

Some users had a spelling checker issue in which every single word was displayed with red squiggles. It turned out that the bdic files were not located in the expected %appdata% directory.
On my local machine the missing files appear at runtime, which apparently does not work for other users. So where does the bdic files in the %appdata% directory come from?

Best regards
Posted: Wednesday, June 5, 2019 11:08:59 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 21,568

We do not officially support such features directly through our API. However we can provide you some implementations details regarding Chromium's dictionary so that you may be able to implement this in your own code.

1. Chromium uses two separate dictionary files. The main dictionary file is in "AppData\Local\EO.WebEngine\User Data\Dictionaries" folder. The dictionary is automatically downloaded from Google if one does not exist. The download can fail due to various reasons: network access, local file permissions, etc. When that fail, you will not get the dictionary file and spell checker will fail on every word. If you run into such issue, you can make sure the file exists in that folder;

2. There is a separate dictionary file named "Custom Dictionary.txt" inside the browser engine's cache file path. This file contains user added words. By default the browser engine's temp file path is in "AppData\Local\Local\Temp\eo.webbrowser.cache.xxxx" where "xxxx" can vary depending on EO.WebBrowser version number and a number of other factors. The easiest way for you to get this path is through this property:


The file contains custom words one word per line, then one additional line that contains the MD5 checksum of all the previous lines. You can reference the chromium source code that reads/writes this file for more details:


So in theory it's possible for you to create a file with all your custom words and place it inside the cache path and they should be automatically picked up by the spell checker.

Hope this helps.


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.