| Summary: | claws-mail with hunspell | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Georges Eckenschwiller <paiiou> |
| Component: | RPM Packages | Assignee: | Julien Moragny <julien.moragny> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | dmorganec, n54 |
| Version: | Cauldron | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://wiki.mageia.org/en/Consolidate_spell_checkers | ||
| Whiteboard: | |||
| Source RPM: | claws-mail | CVE: | |
| Status comment: | |||
|
Description
Georges Eckenschwiller
2011-12-12 10:21:57 CET
Kamil Rytarowski
2011-12-12 12:27:32 CET
CC:
(none) =>
n54 Hi, thanks for reporting this bug. Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it) Keywords:
(none) =>
Triaged Claws mail works with enchant and not aspell directly. It already works without aspell (I just tried). I just need to drop requirement to aspell-dictionary and add one to myspell or hunspell-dictionary. Status:
NEW =>
ASSIGNED Hello, don't add to the myspell. It will be dropped from Mga.
Kamil Rytarowski
2011-12-15 23:27:05 CET
URL:
(none) =>
https://wiki.mageia.org/en/Consolidate_spell_checkers Funda fixed in svn Status:
ASSIGNED =>
RESOLVED He didn't. Now, if you have only an hunspell dictionary installed, it gives you an error message. Ah, I was looking at logs. Reopening We have to rework out hunspell, enchant and dictionaries too. Status:
RESOLVED =>
REOPENED (In reply to comment #5) > He didn't. Now, if you have only an hunspell dictionary installed, it gives you > an error message. which error message ? CC:
(none) =>
dmorganec An error message related to not find dictionary: if you have only hunspell ATM, enchant doesn't detect it and so claws thinks it doesn't have a dictionary and express disagreement when you try to compose a new mail. I just pushed a new package with a requires on enchant-dictionary = 2; ATM it pulls myspell but when hunspell will be fixed it should do the right thing. (feel free to reopen if there is other step I forgot) Status:
REOPENED =>
RESOLVED |