Mailinglist Archive: opensuse-features (226 mails)

< Previous Next >
[openFATE 305688] system wide spellchecker (hunspell)
  • From: fate_noreply@xxxxxxx
  • Date: Tue, 10 Feb 2009 18:04:00 +0100 (CET)
  • Message-id: <feature-305688-5@xxxxxxxxxxxxxx>
Feature changed by: Petr Gajdos (pgajdos)
Feature #305688, revision 5
Title: system wide spellchecker (hunspell)

openSUSE-11.2: New
Requester: Important

Requested by: Kálmán Kéménczy (kkemenczy)

Why Hunspell? MySpell is not developed for quite a long time either in
Mozilla and in Hunspell is a fork of MySpell, it has
great improvements is several ways, and fully backward compatible with
MySpell. Main features: * Extended support for language peculiarities;
Unicode character encoding, compounding and complex morphology. *
Improved suggestion using n-gram similarity, rule and dictionary based
pronounciation data. * Morphological analysis, stemming and generation.
* Hunspell is based on MySpell and works also with MySpell
dictionaries. * GPL/LGPL/MPL tri-license
Fedora project: Ubuntu
project: I also find a
reference in the wishlist:

#2: Petr Mladek (pmladek) (2009-02-06 19:21:04)
In general, I think that it makes sense to have one system speelchecker
(disk space savings, easier maintainability, shared user-specific-
dictionary between applications, ...). I do not know the implementation
details but I heard from more sides that hunspell was the best choice.
It seems that Fedora and Ubuntu are going to use hunspell for this
purpose => we could resuse their solution has already used the system hunspell since openSUSE-
11.1. It used the internal hunspell long time before.

+ #3: Petr Gajdos (pgajdos) (2009-02-10 18:02:44)
+ I don't have any objections. But there are plenty of packages that
+ depends on aspell-devel, aspell or ispell. Question is if this is real
+ dependency or not. For example gtkspell had fake dependency on aspell-
+ devel, because it is linked againist enchant wrapper in fact. Many of
+ them are real, though -- they must be reworked then.

openSUSE Feature:

< Previous Next >
This Thread