Hunspell is not used via libhunspell

[Pander]

Hunspell is not used when myspell is not install, enchant falls back to inferior aspell.

I have installed on Ubuntu (Natty) the following packages:
libenchant1c2a 1.6.0-1
aspell 0.60.6-4ubuntu1
hunspell 1.2.11-1ubuntu1
and a series of dictionaries but no package with the myspell executable.

When using e.g. gedit that uses enchant, enchant will use aspell instead of
hunspell. I have verified this by running both hunspell and aspell manually on
the same document. The false positives that I see in gedit are indeed from
aspell.

I did not use a custom .enchant file, just the normal installation that would
use:
  *:myspell,aspell,ispell
So I would expect hunspell and not aspell.

How can this be solved without having to install myspell executable?

I consider this a major bug because many many users might expect that they are
using a very recent and acurate spell check from hunspell but are actually
thrown back to inferior checking with aspell.

Can enchant bugs be linked to upstream bugzilla bugs in https://bugs.launchpad.net/bugs/bugtrackers/abi-bugs ?

[Pander (pander)]

See also http://bugzilla.abisource.com/show_bug.cgi?id=13082

[Pander (pander)]

Apperently enchant is including its own copy of old hunspell source files. :( This should be fixed as soon as possible so libhunspell is being used instead. For more details, see the abisource bugzilla bug.

[Pander (pander)]

Part of this bug has been changed and partly split off to http://bugzilla.abisource.com/show_bug.cgi?id=13089

Note that Ubuntu users can experience differences in hunspell results when enchant is used as the personal dictionaries for hunspell and enchant are not synced.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[vgeloven (vgeloven)]

Fixed in version 1.6.1 of 14 December 2016, see https://github.com/AbiWord/enchant/pull/15

Please upgrade enchant as this package hasn't been upgraded since at least 2012 in Ubuntu.

[Pander (pander)]

Note that version 1.6.1 is from February 2017, nevertheless, package still needs software upgrade.