48ed320b56
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.
22 lines
1.1 KiB
Text
22 lines
1.1 KiB
Text
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 (intends to replace Ispell)
|
|
* Ispell (old as sin, could be interpreted as a defacto standard)
|
|
* MySpell/Hunspell (an OOo project, also used by Mozilla)
|
|
* Uspell (primarily Yiddish, Hebrew, and Eastern European
|
|
languages - hosted in AbiWord's CVS under the module "uspell")
|
|
* Hspell (Hebrew)
|
|
* Zemberek (Turkish)
|
|
* Voikko (Finnish)
|
|
* AppleSpell (Mac OSX)
|
|
|
|
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.
|