Log message:
enchant2: update to 2.6.9.

Release v2.6.9

This release implements user dictionaries for Nuspell, Voikko and Hspell.

Release v2.6.8

This release better documents the limited capabilities Enchant currently has for \ 
user-specified dictionaries.

Log message:
enchant2: update to 2.6.7.

2.6.7 (February 8, 2024)
------------------------

This version fixes an error introduced in the previous version that caused the \ 
Hunspell provider to fail on startup. Apologies!

2.6.6 (February 4, 2024)
------------------------

This version fixes the implementation and documentation of system paths for
configuration files (enchant.ordering). Since version 2.6.4, the wrong path
was searched for pkgdatadir: not, for example /usr/share/enchant-2, as
documented, but the old path /usr/share/enchant. The enchant(5) man page
referred to “DATADIR” rather than the actual configured path. The sysconfdir
location, typically /etc, was not documented.

Hunspell users should note that, contrary to the NEWS entry for 2.6.5, the
DICPATH environment variable cannot be used to specify the location of
hunspell dictionaries to Enchant. That is because it only works with the
hunspell program (which Enchant does not use), not the hunspell library.

Additional debug logging has been added for developers trying to diagnose
problems with configuration files and providers, which can be enabled at
run-time by setting the environment variable G_MESSAGES_DEBUG to
‘libenchant’.

Log message:
enchant2: update to 2.6.5.

2.6.5 (January 7, 2024)
-----------------------

This version permits error messages from spelling providers not to be valid
UTF-8. This allows error messages in particular about invalid UTF-8
characters in personal wordlists to be shown to the user. Developers take
note!

The --with-hunspell-dir configure option is removed (along with all the
other ---with-PROVIDER-dir options, which did nothing). Users who have
Hunspell dictionaries in non-standard locations should set the
Hunspell-specific environment variable DICPATH, or copy the dictionaries
into their user’s Enchant configuration directory (for example
~/.config/enchant/hunspell).

Doxygen API documentation is now included in the release tarball (it is also
now available online).

Log message:
enchant2: put back applespell lib

Log message:
enchant2: use PLIST.Darwin instead

Log message:
enchant2: fix PLIST

Log message:
enchant2: update to 2.6.4.

2.6.3 (December 11, 2023)
-------------------------

This version makes pkgdatadir versioned by default.

Log message:
enchant2: update to 2.6.3.

2.6.3 (December 2, 2023)
-----------------------

This version fixes a bug in the tests when pkgdatadir is set to a
non-default value, and clarifies the documentation for setting pkgdatadir.

Log message:
enchant2: update to 2.6.2.

2.6.2 (October 28, 2023)
------------------------

This version documents exclude files: each personal word list is paired with
an exclude file that contains words the user considers invalid.

Log message:
enchant2: update to 2.6.1.

2.6.1 (September 24, 2023)
--------------------------

This version tweaks normalization of language tags so that only the part of
the tag that specifies country and language is altered; any extra that is
not removed is left alone. This fixes the use case for Aspell dictionaries
that was fixed in the Aspell backend in 2.6.0. Thanks again to Abdul-Lateef
Haji-Ali for the report and help with the fix.

2.6.0 (September 24, 2023)
--------------------------

This version removes validation of language tags; dictionary names no longer
have to be valid language tags. This is because dictionaries in the wild
sometimes are sometimes not named with valid tags, and so are not visible to
Enchant. Programs that use Enchant will have to cope with this, for the
purposes of working out which languages are supported; but it should not a
big deal, as Enchant already accepted valid language tags with extra stuff
on the end, such as “en_GB-ize”.

Debug output now uses GLib’s debug system, and can be enabled at run-time by
setting the environment variable G_MESSAGES_DEBUG to ‘libenchant’. If you
have had problems understanding why Enchant is not using the spelling
provider you expect, now’s the time to get in touch via the issue tracker
and see if we can work out what’s going on!

The Aspell back-end has a fix to let it work with language variants such as
“en_GB-ize”. Thanks to Abdul-Lateef Haji-Ali for this fix!

There’s more code clean-up, build system updates, and a couple of null
pointer dereference fixes (thanks, GCC!).