Age | Commit message (Collapse) | Author | Files | Lines |
|
the dependencies on aspell and hunspell); added a MESSAGE file mentioning
the need for dictionaries.
|
|
Bug fixes.
|
|
Included hunspell upgraded to 1.2.2, pkgsrc patches integrated.
|
|
Fix path to hunspell directories. Make hunspell the default backend.
Bump PKGREVISION.
|
|
http://bugzilla.abisource.com/show_bug.cgi?id=11550
is fixed.
Add fix for compiling with gcc3, from Adam Hoka.
Bump PKGREVISION.
|
|
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)
|
|
|
|
|
|
|
|
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.
|
|
No PKGREVISION bump since pkg-config is only a BUILD_DEPENDS.
|
|
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.
|
|
|
|
CFLAGS.SunOS+= -D__EXTENSIONS__
This fixes problem where some definitions from <unistd.h>
were not used.
|
|
Bug fixes and better Mac OSX integration.
|
|
|
|
Since dependencies were actually failing to build, they fortunately don't
require PKGREVISION bumps themselves.
|
|
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.
|
|
|
|
|
|
|
|
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that
are automatically handled by the default setting in bsd.pkg.mk.
|
|
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.
|