Bug 132433 – app-text/enchant doesn't work with current ispell dictionaries

• Product: Gentoo Linux
• Status: RESOLVED TEST-REQUEST

[Description Carsten Lohrke (RETIRED) 2006-05-06 03:48:37 UTC]

See https://bugs.kde.org/show_bug.cgi?id=81415

This affects all versions of app-text/enchant. Sent an email upstream already.


Looking at the ebuild the dependencies seem a bit odd. Enchant links to aspell, but to have the dictionaries of the other spell checkers available pure runtime dependencies suffice. Also maybe the user doesn't want en US/GB dictionaries.


I'd say a virtual/ispell-dict and having all app-dicts/ispell-* depend on 
|| ( app-text/ispell app-text/enchant )  - a fixed version of course - is the better way. Probably similar issues with the other spell checkers (didn't look at them).

[Comment 1 foser (RETIRED) 2006-05-21 04:51:13 UTC]

Could you explain your bug exactly.. ? You seem to raise several issues, one about ispell not working with enchant (fair enough) and then something about dependencies here or there (too vague to make out what you mean).

Also you say you put something upstream (what and where?) and something else about not wanting an english dictionary. In short this is just one hell of a bugreport and that from a dev.

[Comment 2 Carsten Lohrke (RETIRED) 2006-06-01 10:01:20 UTC]

> In short this is just one hell of a bugreport and that from a dev.

Sorry. I thought the kde bug would be enough as explanation. Ispell changed (at least four years ago) its dictionary file format and enchant never adapted. I stumbled about it, because of bug 130496.

Yes, I went upstream, but thought it might make sense to make aware about it. The author replied that he'll look to fix it in a coming release of enchant, but that he doesn't know, when he finds the time.


The dependecy issues are disputable and if you want it, I do open another bug, but I thought this would not be necessary.

[Comment 3 foser (RETIRED) 2006-06-02 02:29:01 UTC]

I think the dependencies make sense as it is, after all you need them runtime to spellcheck anything. Yes a virtual to provide a default ispell dictionary makes sense (like aspell does), but that should be filed to the ispell maintainers.

As far as the backends go, I knew not all worked as well, that is why aspell is the primary provider. If ispell does not work at all, it should be removed from the dep list. I am no position to test all backends, I think that is more something our userbase could report (I cannot remember having bugs reported about it).

[Comment 4 Wulf Krueger (RETIRED) 2007-08-18 13:06:39 UTC]

Is this still a problem?

[Comment 5 Carsten Lohrke (RETIRED) 2007-12-23 22:02:37 UTC]

(In reply to comment #4)
> Is this still a problem?
> 

In KDE it's still an issue, as the inluded Enchant version hasn't been been updated afaik. I'm not aware, if this problem has been taken care of in v.1.3.0.

[Comment 6 Gilles Dartiguelongue (RETIRED) 2009-05-07 09:47:47 UTC]

(In reply to comment #5)
> (In reply to comment #4)
> > Is this still a problem?
> > 
> 
> In KDE it's still an issue, as the inluded Enchant version hasn't been been
> updated afaik. I'm not aware, if this problem has been taken care of in
> v.1.3.0.
> 

would be nice if kde could use system's enchant.

[Comment 7 Samuli Suominen (RETIRED) 2009-10-22 19:19:00 UTC]

I think this problem will go away when KDE3 goes away.. adding kde@ to track this issue

[Comment 8 Romain Perier (RETIRED) 2009-11-06 17:21:53 UTC]

enchant works only with myspell-fr here...

[Comment 9 Samuli Suominen (RETIRED) 2009-11-07 20:15:39 UTC]

As far as KDE is concerned, this is no longer a issue for us (unless proven otherwise) with the KDE 3.5.10 masking today.

[Comment 10 Serkan Kaba (RETIRED) 2010-04-11 06:19:20 UTC]

Please test with newer versions and reopen if this is still an issue.