Problems found locating distfiles:
Package cabocha: missing distfile cabocha-0.68.tar.bz2
Package convertlit: missing distfile clit18src.zip
Package php-enchant: missing distfile php-enchant/enchant-1.1.0.tgz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
* Fix bug 12567: the ispell sources aren't licensed under the LGPL
* Add a function to get enchant's version (enchant_get_version)
* Disable zemberek plugin by default, as it's known to cause issues/crashes with WebKit
* Fix bug 12472: Win32 DLL dependency not found popup occurs when module has unmet dependencies
* Possibly fix Ubuntu bug 474062
* Fix bug 12409: Registry handle not closed in enchant_get_registry_value_ex
* Fix bug 12406: Leak in _enchant_get_user_home_dirs() on Windows
* Fix bug 12007: Update FSF address
* Fix bug 12305: Zemberek module lists a Turkish dictionary even without Zemberek installed
* Don't assert if passed a null string list
* Fix bug 12350: enchant_pwl_init_with_file truncates pwl file
* Fix a double-free memory corruption bug
* Fix bug 12173: fix some small memory leaks
* Fix bug 12174: mis-acceptence of dictionaries which start with a partial match of the lang id
* Fix bug 12160: enchant 1.5.0 always looks in "lib" dir for plugins
* Fix the build with the MSVC compiler
* Add a --with-system-myspell option
* Package missing compile-resource file
* Compare paths ignoring case sensitivity on windows
Change default backend to hunspell.
aspell support is now a (disabled by default) option.
Add some other options.
Remove aspell from includes in buildlink3.mk. The backends
are abstracted into dynamically loaded modules and don't need
to be pulled in by buildlink3.mk.
Release notes:
Voikko (Finnish) language support. Zemberek (Turkish) language support.
Better support for Unicode in the personal dictionaries. Personal
dictionaries offer better suggestions. OpenOffice's dictionaries are used
on Windows. Aspell works on Windows. This release can use a system-wide
Hunspell/Myspell installation on Unix-like platforms. Hunspell 1.2.1 and
NET bindings are required. This release has more lax language matching
rules. It uses XDG's data-dirs spec for locating dictionaries. There are
many unit tests and bugfixes.
This stable release includes updated documentation, relocatable
binary support, better Aspell support, Hunspell support (replacement
for Myspell), Hspell support, and some minor bugfixes.
New in 1.2.3:
Bug fixes.
New in 1.2.1:
Better support for aspell-0.50 and greater
Hunspell support
Better Hspell support
The usual pile of bugfixes
(other changes unknown)
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:
:)
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.
