Community
Participate
Working Groups
When using a custom spelling engine extending org.eclipse.ui.workbench.texteditor.spellingEngine with the Java editor the custom spelling engine is used to find spelling errors, however proposed changes are retrieved from the default spelling engine. The custom spelling engine org.eclipse.ui.texteditor.spelling#SpellingProblem implementation is asked for position and the description about the spelling problem, however SpellingProblem#getProposals is never called. Instead JavaQuickFix#getCorrections always uses org.eclipse.jdt.internal.ui.text.spelling#SpellCheckEngine to get the proposals.
The custom engine is responsible to create (or implement) the problems which then return the proposals. If you still see this problem using 4.3 M7 [1], then please attach a sample plug-in with a custom spelling engine and steps to reproduce the problem. >JavaQuickFix#getCorrections This method does not exist in the SDK. [1] http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M7-201305020800/
Created attachment 230528 [details] Sample plug-in
Same problem, the call to default spelling engine now (in org.eclipse.jdt.ui_3.9.0) comes from org.eclipse.jdt.internal.ui.text.spelling.WordQuickFixProcessor. final ISpellCheckEngine engine= SpellCheckEngine.getInstance(); final ISpellChecker checker= engine.getSpellChecker(); With the spelling engine in the attached sample plug-in the word "proposal" is always considered misspelled. In an ordinary text editor "proposal 1", "proposal 2", "proposal 3" is proposed. In a Java editor "proposal" and "proposals" is proposed.
Requested example uploaded
WordQuickFixProcessor#getCorrections should ask the CoreSpellingProblem for the proposals and this should delegate to the original SpellingProblem.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Still valid as of 4.14.
