NuGet
Use a custom spell-check engine
Plug an application-owned spelling engine into the same review workflow used by the native editor. Implement the shared ISpellCheckerEngine contract, then select Custom mode.
An engine instance has one active native editor owner; give independent editors separate engine instances.
Use it in your application
The engine in the example is your implementation of the shared spelling interface. Inspect the package API for its exact methods before implementing it.
Supply predictable local behavior for checking, suggestions and disposal. Keep slow network work out of synchronous spelling calls.
Test cancellation, document changes and custom-word policy with the engine you deploy. The editor cannot infer those behaviors from an interface declaration.
editor.SpellCheckOptions.CustomSpellCheckerEngine = engine;
editor.SpellCheckOptions.SpellChecker = SpiceLogic.HtmlEditor.Abstractions.Entities.SpellCheck.SpellCheckerEngineTypes.Custom;Members
These signatures come from the delivered 1.0.2 assemblies and XML documentation. Cancellation tokens can be supplied to awaited operations. Follow the source-specific notes above when adapting a WPF integration.
| Member | Signature |
|---|---|
AddToUserDictionary | void AddToUserDictionary(string word) |
Dispose | void Dispose() |
Initialize | void Initialize(string dictionaryPath, string affixPath, string userDictionaryPath) |
Spell | bool Spell(string word) |
Suggest | IEnumerable<string> Suggest(string word, Nullable<int> max) |