Issue 116270 - oracle.dic introduces false good words in all languages
Summary: oracle.dic introduces false good words in all languages
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: configuration (show other issues)
Version: OOo 3.3 RC8
Hardware: All All
: P3 Trivial (vote)
Target Milestone: 3.4.0
Assignee: stefan.baltzer
QA Contact: issues@sw
URL:
Keywords: oooqa, regression
Depends on:
Blocks:
 
Reported: 2010-12-31 09:16 UTC by jumbo444
Modified: 2017-05-20 10:30 UTC (History)
7 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description jumbo444 2010-12-31 09:16:20 UTC
Hello,

Since OOo 3.3, oracle.dic is added at installation time as personal dictionary.
Then a lot of words are considered as correct in all languages.
For instance in French:
Education instead of Éducation
Edition instead of Édition
Enterprise instead of Entreprise
and so on.

Either this dictionary should be removed or at least it contains too many words.
Comment 1 eric.savary 2010-12-31 11:11:12 UTC
@VA: Please check why we now added the half English dictionary (for all
languages) to the oracle.dic custom dictionary.
AFAIK this dictionary should only ignore trade mark names and people names but
not every (common) English word found in any license or trade mark name.

This partly destroys the spell check functionality in other languages than English.

Seeing this as a regression (introduced in 3.3)

CC: SBA/TL. 
Comment 2 jbf.faure 2011-01-03 05:41:35 UTC
Add me to cc.
Comment 3 thomas.lange 2011-02-09 12:01:44 UTC
TL->ES: AFAIR VA added those words because there was a requirement that a huge
list of words (taken from some other dictionary that was provided by Oracle)
should never be marked as incorrect. 

TL->jumbo444: work-around disable the 'oracle.dic' dictionary.
Comment 4 weko 2011-02-09 12:11:28 UTC
I will talk to SBA and GW (Goetz Wohlberg) regarding this issue.
Comment 5 eric.savary 2011-02-09 12:58:43 UTC
Proposal: come back to a dictionary including *only* *full* trade marks and
reserved named.
Ex: if a trade mark would be "AssetMaker", include "AssetMaker" which is an
unknown word (at least in English).
Don't include "Asset" and separately "Maker" which are common words and no trade
marks which can collide with foreign words.

Comment 6 jumbo444 2011-02-09 13:28:32 UTC
jumbo444->TL: I knew this workaround. The problem is that user may falsely
accused dictionary extension to not detect some errors.
Comment 7 rafaella.braconi 2011-02-15 14:40:59 UTC
.
Comment 8 weko 2011-03-21 10:05:36 UTC
Started.
Comment 9 weko 2011-03-22 15:35:52 UTC
Fixed in CWS extras340.
Comment 10 stefan.baltzer 2011-03-23 17:33:30 UTC
Verified in CWS extras340.