Commit graph

6 commits

Author SHA1 Message Date
Jack Nagel
54fea7d0fa enchant: depends on pkg-config 2013-02-10 00:28:09 -06:00
Jack Nagel
7326359cf9 enchant: only build aspell backend
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
2012-08-17 22:18:15 -05:00
Adam Vandenberg
4147b05c57 Use ruby style for inheritance. 2011-03-12 11:55:09 -08:00
Alexis Hildebrandt
5d33729926 Update Formula: enchant
Version bump to 1.6.0

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
2010-07-27 15:28:21 -07:00
Martin Kühl
06b3b3a3e6 enchant depends on glib
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
2010-03-16 11:28:13 -07:00
Alexis Hildebrandt
3b6260804d Enchant 1.5.0
On the surface, Enchant appears to be a generic spell checking library.
You can request dictionaries from it, ask if a word is correctly
spelled, get corrections for a misspelled word, etc...

Beneath the surface, Enchant is a whole lot more - and less - than that.
You'll see that Enchant isn't really a spell checking library at all.

"What's that?" you ask. Well, Enchant doesn't try to do any of the work
itself. It's lazy, and requires backends to do most of its dirty work.
Looking closer, you'll see the Enchant is more-or-less a fancy wrapper
around the dlopen() system call. Enchant steps in to provide uniformity
and conformity on top of these libraries, and implement certain features
that may be lacking in any individual provider library. Everything
should "just work" for any and every definition of "just working."
2010-01-23 12:21:14 +00:00