Mailinglist Archive: opensuse-features (226 mails)

< Previous Next >
[openFATE 305688] system wide spellchecker (hunspell)
  • From: fate_noreply@xxxxxxx
  • Date: Wed, 11 Feb 2009 22:10:59 +0100 (CET)
  • Message-id: <feature-305688-11@xxxxxxxxxxxxxx>
Feature changed by: Scott Couston (zczc2311)
Feature #305688, revision 11
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.
* 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.

#4: Scott Couston (zczc2311) (2009-02-10 21:36:17)
Apart from the purely technical aspect, Myspell offers very very poor
English US and slightly better English UK suggestion choice and is
hugely dependent on the user getting the first two letters correctly
spelt speelt spellt in the word that is mispellt. - English is such a
poorly constructed language when it comes down to conventions that
always apply. There is very little logic in the English Language so
without * Improved suggestion using n-gram similarity, rule and
dictionary based pronounciation data. * Morphological analysis,
stemming and generation MySpell is very poor. - The other notable drag
with the very very poor UK dictionary that still gets confused between
US/UK words - and there is a huge difference. Quite often I cut and
past into Open Office as the spell checker and word choice offerings
are just so much better - in every sense. I would love to see us use
the same spell checker and language modules that Open Office use so we
can stop relying on other dictionary modules being developed and make
use of the continual development that is done for us by OO. - Love the
1 dictionary, love the continuity idea, but rather than reinvent
dictionary modules can we not use OO and its spell checker process.

#5: Petr Mladek (pmladek) (2009-02-11 11:35:57) (reply to #4)
I see that we have started to use hunspell in by default
since OOo-2.0 and January 2006. I am surprized that there is such a big
difference between myspell and hunspell but... In each case, it looks
like you have a good experience with hunspell.

+ #6: Scott Couston (zczc2311) (2009-02-11 22:10:48)
+ My PC always has a copy of OO Writer Open - I write all the text
+ anywhere else and before I commit I cut and paste to OO then correct
+ spelling and cut and paste back into dialog - Its that bad - and the
+ worst thing is the enormous amount of personal dictionaries any use can
+ have - I think we are up to about 7 or so user specific dictionaries
+ counting OO ;-)
+ Other advantages are there is an abundant number of localised .LEX(?)
+ files available for OO/FireFox/Thunderbird

openSUSE Feature:

< Previous Next >
This Thread