On Tue, 27 Mar 2012 12:04, Ismail Dönmez
On 03/23/2012 10:41 AM, Cor Blom wrote:
KDE is built with both aspell and enchant support. Enchant is a frontend for different backend (hunspell/myspell is default, but the package in openSUSE has also support for aspell, ispell and a few more specialised backends). KDE does not have a real interface to choose between aspell of enchant. You can only choose the language and when both aspell and myspell dictionaries are installed, you get two possibilities for each language and only through some experimenting you can discover which choise belong to which spellchecker backend. Not really user friendly.
I would like to do a SR to remove aspell from the BuildRequires in kdelibs4. KDE is then build only with enchant. I already did an experimental build in home:cornelisbb:spellcheck and did not discover any problems. But first I like to ask for some feedback.
The choice for enchant is to be preferred, because hun/myspell is then default. A combination of hunspell and enchant is then used systemwide as default in the most important apps: firefox, thunderbird, libreoffice, gnome. Installing the myspell dictionaries is then enough.
I want to accept this SR for 12.2, any objections?
I'm all for it. Maybe aspell is better than ispell on english, but I could not proof that. Both ispell and myspell are fine for my uses. Removed aspell by hand on a OSS 11.2 + KR:46, and on OSS 12.1. Both times it worked fine, no loss of any functionality, other than broken dependencies in kdelibs and enchant. For info: aspell is also 'required' by librcc0, which in turn is required by unzip, could that also be changed to enchant, maybe? Q: How is the situation on Gnome? AFAIK it works fine without aspell. IMO target for OSS 12.2 could be no aspell in default install. At least no direct depenency. Enchant should ask for at least one of (ispell, myspell, hunspell, aspell) but not force the install of all. More like plugins, "can use but not need more than one". Cheers, Yamaban.