Issue 14817 - Spellcheck doesn't initially consult standard.dic
Summary: Spellcheck doesn't initially consult standard.dic
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 Beta2
Hardware: Other Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: khendricks
QA Contact: issues@sw
URL:
Keywords:
Depends on: 15362
Blocks:
  Show dependency tree
 
Reported: 2003-05-23 21:14 UTC by stamp
Modified: 2013-08-07 14:44 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description stamp 2003-05-23 21:14:43 UTC 
Typing words that are in standard.dic will still be considered spelling errors by 
spellcheck until you right click on one misspelled word to see alternate spellings.   
 
Once you right click, it seems like standard.dic is consulted, and any word in the 
list is no longer considered a spelling error.
Comment 1 khendricks 2003-05-23 21:28:09 UTC 
Hi, 
 
This is actually an issue for the writer project and not lingucomponent. 
 
I am redirecting your issue to there. 
 
Kevin
Comment 2 h.ilter 2003-05-28 10:04:47 UTC 
Reassigned to MRU
Comment 3 michael.ruess 2003-06-04 08:52:20 UTC 
MRU->TL: this might be related to issue #14815 (autospellcheck option
not persistent). The user-defined dictionarys are not activated initially.
Comment 4 thomas.lange 2003-06-06 13:03:05 UTC 
It is not related to the autospellcheck option.
Though the source of the problem is the same.

TL->Kevin: To you since it depends on the fixed setup entry.
Comment 5 khendricks 2003-06-06 13:33:32 UTC 
Hi, 
 
My bug in scp was fixed by another change yesterday so this one should be good to 
go. 
 
So I am resolving this as fixed, please verify in the next OOo 1.1 release. 
 
Thanks for your bug report! 
 
Kevin
Comment 6 khendricks 2003-06-22 13:24:52 UTC 
Hi, 
 
Changing the status of this to resolved as fixed. 
 
It is related to bug 15362. 
 
Thanks, 
 
Kevin
Comment 7 Martin Hollmichel 2004-02-15 07:28:17 UTC 
verfied in 1.1.0.
Comment 8 Martin Hollmichel 2004-02-15 07:31:29 UTC 
close issue