Page History
Excerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
3. Create custom dictionary3.1. Create custom dictionary for default language
Here is an example of CustDictConfig.xml with two global custom dictionaries. One for American English and the other for British English.
Option B. Compiled dictionary
3.2. Create custom dictionary for additional language
4. Enable custom dictionary in web appDepending on the product and where it is integrated, pass an appropriate custom dictionary parameter with a required dictionary ID (DicId) as a value on your web-page.
5. Create shared global custom dictionariesIf you have or plan to run many copies of WebSpellChecker Server in your infrastructure, and your infrastructure is dynamic (for example, you need to add or terminate the servers depending on the workload), you may want to create a centralized folder with global custom dictionaries to store them in a permanent location. There is no default functionality available for this, however, we can share our approach we have already implemented in the Cloud version. Follow these steps:
|