Community
Participate
Working Groups
Build ID: M20080911-1700 The spell checker is currently hard-coded to use the locale specified in the preferences, which makes doing anything else difficult. For example, consider editing resource bundles *.properties. Currently it spell checks only against the current locale so foo_de.properties is flagged with lots of spelling mistakes. Ideally it would spell check against the bundle's locale, provided a suitable dictionary is installed for that locale. ===== What I'm actually doing is using spell check in an RCP application that contains text written in multiple different languages. Its possible to do this but not without @SuppressWarnings("restriction"), I had to subclass SpellingReconcileStrategy and have it swap the locale preference on each call to reconcile. This is not a nice thing to have to do I think you'll agree! It hopefully wouldn't be too hard to change the API to add extra methods that are parameterised by a locale, where the only difference is whether we use the spelling preference or some other criteria to determine the locale.
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.
