Peter Oliver wrote:
If we’re going to recommend migration to anything, shouldn’t it be
enchant2? Users would be able to configure their preferred spellchecking
engine per language (which I imagine is more important for some languages
than others), and we wouldn’t have to go through this again in the future
if we hypothetically decided that, say, Nuspell should replace Hunspell as
our default spellchecker.
It shall be noted that KDE upstream actually dropped Enchant support in
Sonnet in KF5 and switched to using Hunspell directly. (They also support
aspell, hspell, and voikko. All 4 are optional at compile-time, and plugins
at runtime.) Though to be fair, Sonnet is already an abstraction similar to
Enchant, and having an abstraction built on top of an abstraction apparently
did not work out that well.
Kevin Kofler