Issue 96239 - Cannot (permanently or reliably) disable the Mac OS X Spell Checker
Summary: Cannot (permanently or reliably) disable the Mac OS X Spell Checker
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 3.0
Hardware: Mac Mac OS X, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2008-11-15 16:52 UTC by gonhidi
Modified: 2013-01-29 21:50 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description gonhidi 2008-11-15 16:52:04 UTC
The "Mac OS X Spell Checker" cannot be (reliably or permanently) disabled.

I would like to be able to disable's use of the Mac OS spell
checker. The rest of the language modules ("Hunspell SpellChecker", "Libhyphen
hyphenator" and " New Thesaurus") seem to have their settings
apply permanently to all documents and across sessions. The Mac OS X module
however, never stays disabled for long.

Steps to reproduce:
    1.- Start
    2.- Open " -> Preferences".
    3.- Go to "Language Settings -> Writing Aids", and uncheck "Mac OS X Spell
    3.- Press OK
    4.- Open "Preferences" again (or do so a couple of times).

Result: The "Mac OS X Spell Checker" writing aid option is checked (enabled).

Expected result: The "Mac OS X Spell Checker" writing aid option should stay
unchecked (disabled).

Observation: When editing a document (for example through Writer), the Mac OS X
spell checker can be disabled. However, opening the application preferences in
the same document or in another one will reset it (even if no change is applied
in the preferences).
Comment 1 Olaf Felka 2009-04-30 10:18:54 UTC
@ sba: Please have a look.
Comment 2 gonhidi 2009-05-01 12:55:34 UTC
After some time not caring about the problem, I have seen that with OOo 3.1.0RC2
does not seem to show the reported behaviour.

I am having crashes when going back to OOo 3.0.0 so I can't confirm whether it
was specific to that version, but it might be so since I haven't managed to
reproduce it with OOo 3.0.1.