summaryrefslogtreecommitdiff
path: root/textproc/enchant/Makefile
AgeCommit message (Collapse)AuthorFilesLines
2008-10-13Add a dependency on ispell-base if ispell is enabled (parallel tosmb1-1/+2
the dependencies on aspell and hunspell); added a MESSAGE file mentioning the need for dictionaries.
2008-05-21Update to 1.4.2:wiz1-3/+3
Bug fixes.
2008-04-22Update to 1.4.1:wiz1-7/+3
Included hunspell upgraded to 1.2.2, pkgsrc patches integrated.
2008-04-17Fix hunspell backend. Idea from Matthias Drochner, patch from Adam Hoka.wiz1-2/+4
Fix path to hunspell directories. Make hunspell the default backend. Bump PKGREVISION.
2008-04-17Make aspell the default backend again (for now), untilwiz1-2/+6
http://bugzilla.abisource.com/show_bug.cgi?id=11550 is fixed. Add fix for compiling with gcc3, from Adam Hoka. Bump PKGREVISION.
2008-04-14Update to 1.4.0.wiz1-4/+5
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.
2006-12-05Update to 1.3.0:wiz1-3/+3
This stable release includes updated documentation, relocatable binary support, better Aspell support, Hunspell support (replacement for Myspell), Hspell support, and some minor bugfixes.
2006-11-14DESTDIR support.joerg1-1/+3
2006-10-04Update MASTER_SITES and/or HOMEPAGE, from Sergey Svishchev.wiz1-2/+2
2006-07-12Update to 1.2.6:wiz1-4/+3
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)
2006-06-15Drop maintainership, I don't use them any longer.wiz1-2/+2
2006-05-09Add missing USE_LANGUAGES.hira1-1/+2
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg1-1/+2
2005-08-10Remove the abuse of buildlink that was pkg-config/buildlink3.mk. Thatjlam1-2/+2
file's sole purpose was to provide a dependency on pkg-config and set some environment variables. Instead, turn pkg-config into a "tool" in the tools framework, where the pkg-config wrapper automatically adds PKG_CONFIG_LIBDIR to the environment before invoking the real pkg-config. For all package Makefiles that included pkg-config/buildlink3.mk, remove that inclusion and replace it with USE_TOOLS+=pkg-config.
2005-07-21Change path from devel/pkgconfig to devel/pkg-config.wiz1-2/+2
No PKGREVISION bump since pkg-config is only a BUILD_DEPENDS.
2005-04-13update to 1.1.6:drochner1-3/+3
This release features the ability to get a list of supported languages, and the usual bugfixes. A few APIs have been deprecated in the process.
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-15Add support for Solaris with:reed1-1/+2
CFLAGS.SunOS+= -D__EXTENSIONS__ This fixes problem where some definitions from <unistd.h> were not used.
2005-01-06Update to 1.1.5:wiz1-3/+2
Bug fixes and better Mac OSX integration.
2004-12-24Bump PKGREVISION for aspell dependency update.wiz1-2/+2
2004-10-07Extra PKGREVISION bump to cover the libtool/compiler-wrapper problems.tv1-2/+2
Since dependencies were actually failing to build, they fortunately don't require PKGREVISION bumps themselves.
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv1-1/+2
in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include.
2004-02-23Explicitly depend on pkgconfig.minskim1-1/+2
2004-02-15Convert to buildlink3.wiz1-4/+4
2004-02-14PKGCONFIG_OVERRIDE is relative to WRKSRC.jmmv1-2/+2
2004-02-14LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now lists of shell globsjlam1-2/+1
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that are automatically handled by the default setting in bsd.pkg.mk.
2003-12-26Update to 1.1.3:wiz1-3/+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: :)
2003-09-17Initial import of enchant, a generic spell checking library.wiz1-0/+21
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.