Log message:
Convert to buildlink3.

Log message:
PKGCONFIG_OVERRIDE is relative to WRKSRC.

Log message:
LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now lists of shell globs
relative to ${WRKSRC}.  Remove redundant LIBTOOL_OVERRIDE settings that
are automatically handled by the default setting in bsd.pkg.mk.

Log message:
Update to 1.1.3:
1.1.3:
Now with shiny new Hspell support (requires hspell
0.7). Other than that, no changes have been made since
the 1.1.2 release.

1.1.2:
Has Jordi's Ispell bugfix in it plus the new Hspell
backend.

1.1.0:
New Enchant release. This fixes some
ispell-compatibility mode problems (i.e. the command
line program), specifically related to charsets.

This also fixes some other charset issues that
affected our Ispell and Myspell backends. Big thanks
to Raphael Finkel and egmont@uhulinux.hu (Egmont
Koblinger)

Everyone is strongly encouraged to upgrade. It exports
1 more function and maintains API/ABI compability.
AbiWord 2.1.0 depends on this released version or a
CVS equivalent.

1.0:
:)

Log message:
Initial import of enchant, a generic spell checking library.

The project aims to provide an efficient extensible abstraction
for dealing with different spell checking libraries.

Enchant is meant to provide a generic interface into various existing
spell checking libaries. These include, but are not limited to:
        * Aspell/Pspell
        * Ispell
        * Hspell
        * Uspell

Enchant is also meant to be used in a cross-platform (XP) environment.
Part of this means that Enchant wants to limit its number of external
dependencies to 0, or as close is as humanly possible. Also, any
enchant consumer (i.e. a Word Processor) should not need to know
about what backend providers Enchant knows about. In fact, Enchant
shouldn't even need to know this information itself. To accomplish
this, all of Enchant's providers are DLLs.

Enchant is also meant to be used in a multi-user environment, such
as Unix.  It is preferable to have both a $USER and a $GLOBAL
location for both provider DLLs and for dictionaries themselves,
when possible. Enchant's DLL location algorithm takes this into
account, and gives preference to the $USER DLLs, when found.