Log message:
enchant2: update to 2.8.16.

2.8.16 (May 1, 2026)
--------------------

This release fixes a bug introduced in 2.8.14: after rejecting a word for
not containing at least one letter, enchant(1) would skip the rest of the
line.

Log message:
enchant2: update to 2.8.15.

2.8.15 (February 13, 2026)
--------------------------

This release fixes two bugs related to personal word lists.

First, removing a word that happens to be at the end of a personal word list
file has not worked since 2.7.0.

Secondly, the way that personal word lists are merged with the current
session has been changed so that personal word list words now appear in
suggestions with providers that support adding words to the current session
(Aspell and Hunspell). This previously worked, but hadn’t since at least
2.8.2. Thanks to the users and maintainers of jinx (spelling package for
Emacs that uses Enchant) for reporting and helping reproduce this bug.

A little code clean-up was also done.

Log message:
enchant2: update to 2.8.14.

2.8.14 (November 20, 2025)
--------------------------

This release fixes a test failure in the previous release, and improves
enchant(1)’s word division algorithm, so that it only considers words that
contain at least one letter. (Words may contain characters that aren’t
letters, but Enchant was for example considering “1900” to be a word, which
is probably not helpful.)

2.8.13 (November 19, 2025)
--------------------------

This release fixes a bug in the word division algorithm of enchant(1)
introduced in 2.8.4, which itself was attempting to fix bugs introduced in
the previous release. This could have caused a crash, but it seems we were
saved by careful bounds checking in GLib. Instead, it merely meant that
characters not valid at the end of a word were not removed as they should be
before spell-checking.

Note that this bug only affected users of the enchant(1) program, for
example Emacs users using it via Emacs’s “ispell” command. Users using
libenchant (i.e. most users) were not affected.

Log message:
*: recursive bump for pcre2

Running an old binary against the new pcre doesn't work:
/usr/pkg/lib/libpcre2-8.so.0: version PCRE2_10.47 required by \ 
/usr/pkg/lib/libglib-2.0.so.0 not defined

Log message:
enchant2: update to 2.8.12.

2.8.12 (July 28, 2025)
----------------------

This release fixes a crash introduced in the previous release, where a
dictionary could have a dangling reference to a provider.

Log message:
enchant2: update to 2.8.11.

2.8.11 (July 22, 2025)
----------------------

This release fixes a crash when an empty language tag is given, for example
to `enchant-2 -p`.

Various aspects of the internal provider API have been simplified, and an
obsolete header file removed.

Log message:
enchant2: adjust PLIST.Darwin to match installed .so.

Log message:
enchant2: update to 2.8.10.

2.8.10 (June 21, 2025)
----------------------

This release fixes a crash bug and some space leaks in the Hunspell provider
that were introduced in 2.8.7.

Thanks to @haansn08 and @mike-fabian for the report and debug information.

The handling of PWL dictionaries has also been simplified slightly.

2.8.9 (June 17, 2025)
---------------------

This release fixes a critical bug in the Aspell provider that crept into
2.8.7. Thanks to @hamkg for the report and @chenrui333 analyzing the
problem.

A test has been added that simply runs `enchant-lsmod -list-dicts`, which
would have caught this bug and the double-free fixed in the previous
release.

2.8.8 (June 16, 2025)
---------------------

The previous release had a “double-free” bug that typically caused a crash
on application start-up. Thanks to @AdamWill of Fedora for a quick bug
report that enabled me to locate and instantly fix the bug (apologies!).

A test to detect this sort of bug in future will be forthcoming.

2.8.7 (June 15, 2025)
---------------------

This release stops the Hunspell provider from doing partial matching of
dictionary tags. This fixes an odd situation where it was possible for
Aspell to have an actual “en” dictionary, which would be shown by
enchant-lsmod(1), but when requesting that language, if Hunspell was
configured to take precedence over Aspell, and there was, for example, an
“en_US” dictionary installed for Hunspell, then that would be used. Thanks
to @digitcrusher for filing the bug and helping with the solution.

The providers code has been formatted more consistently, simplified in
places, and made more robust when memory allocation fails. Thanks again to
@digitcrusher for spotting some simplifications I missed.

The minimum version of GLib required is now 2.76, which is quite recent
(from a bit over 2 years ago at the time of writing). Use of this enables
some deprecated APIs to be dropped, and some slight code simplification.

Finally, the compiler warnings used with GCC have been adjusted to turn off
useless warnings, especially for Vala-generated C.