[opensuse-kde] aspell
Hi, 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. Regards Cor -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/23/2012 10:41 AM, Cor Blom wrote:
Hi,
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? Regards. - -- Ismail Dönmez - openSUSE Booster SUSE LINUX Products GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPcZC7AAoJEJrs5hT7LFEc3BwIAMGIj/ZxrW4Un5ZyD+QGRqTQ g48IzY/EuDR7DJm+0wDf+Q8zXDpps1D7G1+n9LTVfrR5jdU85R/wcCWNLpaJll2O kKNTvv7UWURRVAKbLL/km3H8lsBQoqdgDCpglYTWctGi13dqQr9+A3Z7SKiU6aLP M/1Fs3FceoZRiLS5SO3drgaSnU8YJi+Sn6vWmE8oVlyHS9Ph1oSl0sg5Mo9oNTd3 LW+TJn9IwATHdNXk/zHhIOpNkzWHvUr8tN/51BfRiFpaLbUqAy9X9WzF6rjuvM80 8H/6tRXfDvP5A30DTDgNNQPusOu0VSTJUQCoM9qJl6Ao3DRS0w+BC1TAkULt+aU= =OxZC -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
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.
Op dinsdag 27 maart 2012 13:57:52 schreef Yamaban:
Q: How is the situation on Gnome? AFAIK it works fine without aspell.
gnome uses enchant
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".
This is a packaging issue in enchant package. The hunspell/myspell, aspell and ispell backends/plugins are part of the main package, with some more specialised backend in separate packages. Fedora e.g. has only the hunspell backend in the main package and aspell in a separate one, but they have made a more explicit effort to standardise their system on hunspell some time ago. Cor -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Dnia wtorek, 27 marca 2012 12:04:43 Ismail Dönmez pisze:
On 03/23/2012 10:41 AM, Cor Blom wrote:
Hi,
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?
How is GNOME an important application for KDE? Otherwise, all your most important applications (you failed to mention GIMP) depend on Gtk. I perceive it as a failure of the KDE project as such. That is, we give you KDE and we support it but then we have to back off because it does not really work. Chris -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (4)
-
Cor Blom -
Ismail Dönmez -
Křištof Želechovski -
Yamaban