Check kits
Configure which engines run for a language, and which kit is the default.
A check kit is a named proofreading profile.
It defines:
which engines run for a language
engine options (locale, dictionaries, models)
engine priority when results overlap
Check kits are configured per language in AppServerX.xml.
Where check kits are used
On-premise / self-hosted: the language default check kit can be modified in the configuration.
API / client override: you can override the default per request with the
check_kitparameter.
Related:
Default check kit behavior
Most languages ship with a single predefined kit.
Some languages ship with multiple kits.
The usual default is
lt_hs.If AI is installed for a language, the
ai_lt_hs1kit is typically enabled and set as default.
Check kit inheritance
A check kit can inherit from another one with Parent="...".
Parent kit settings are copied first.
Child kit settings override the parent.
Example:
ai_lt_hs1inherits fromlt_hsai_lt_hs0inherits fromai_lt_hs1and disables Hunspell suggestions
Engine priority
Engines have a Priority attribute.
Higher number means higher priority.
Related:
Change the default check kit for a language (self-hosted)
You do it in AppServerX.xml.
You then restart AppServer.
Keep exactly one kit with Default="true" per language.
Make sure the chosen kit is Enabled="true".
Edit AppServerX.xml
Open AppServerX.xml.
Find the target language:
Inside <SupportedCheckKits>, set Default="true" on the kit you want.
Remove Default="true" from the previous default kit.
Example: switch default from lt_hs to ai_lt_hs1
Example: switch default back to lt_hs
If the XML becomes invalid, AppServer may fail to start.
If that happens, check AppServer logs for the exact parse error.
Related:
Was this helpful?

