Spellcheck no longer works with --enable-system-hunspell
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
People
(Reporter: psychonaut, Unassigned)
References
Details
I package SeaMonkey for openSUSE and we use ac_add_options --enable-system-hunspell in the .mozconfig file. This has worked for us up to and including SeaMonkey 2.53.15. Starting with SeaMonkey 2.53.16b1, building SeaMonkey this way results in a non-functional spellchecker. SeaMonkey still finds all the system dictionaries, and allows the user to select among them, but no matter which dictionary is selected, all words to be spellchecked are shown with a red wavy underline. Meanwhile, the following sorts of error messages are printed to the system console:
error: file:///usr/share/myspell/de_AT.aff: cannot open
error: file:///usr/share/myspell/de_AT.dic: cannot open
error: file:///usr/share/myspell/de_AT.aff: cannot open
error: file:///usr/share/myspell/en_US.aff: cannot open
error: file:///usr/share/myspell/en_US.dic: cannot open
error: file:///usr/share/myspell/en_US.aff: cannot open
error: file:///usr/share/myspell/en_GB.aff: cannot open
error: file:///usr/share/myspell/en_GB.dic: cannot open
error: file:///usr/share/myspell/en_GB.aff: cannot open
Removing ac_add_options --enable-system-hunspell from .mozconfig restores the intended behaviour. (Interestingly, this is exactly the opposite of the workaround reported for Bug 1729113, which describes exactly the same symptoms.)
Some searching turns up Bug 1460600, which indicates that --enable-system-hunspell was removed from Firefox 62. Has this change been backported to SeaMonkey 2.53.16b1? If so, or if some similar change has been applied, perhaps this should be mentioned in the release notes so that users and packagers know not to use this option any more.
| Reporter | ||
Updated•2 years ago
|
| Reporter | ||
Comment 1•2 years ago
|
||
I should perhaps clarify that, as in Bug 1729113, the files mentioned in the console error messages do in fact exist and are world-readable. (Well, technically they are symbolic links to world-readable files.)
Comment 2•2 years ago
|
||
Seems a byproduct of Bug 1410214 which added support for webextension dictionaries. I missed Bug 1460600. Will see that it gets in too. So yes no longer supported.
Comment 3•2 years ago
|
||
Bug 146600 has been backported. This is no longer supported.
Updated•9 months ago
|
Description
•