Issue 7689 - Odd behaviors of the spellchecker while using 2 dictionaries and a single affix file
Summary: Odd behaviors of the spellchecker while using 2 dictionaries and a single aff...
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: whiteboard (show other issues)
Version: unspecified
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: khendricks
QA Contact: khendricks
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-09-12 09:25 UTC by luctur
Modified: 2012-02-20 02:24 UTC (History)
1 user (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 luctur 2002-09-12 09:25:54 UTC
Recently, the Italian dictionary is released with an additional dictionary
called comuni.dic (attached to this issue) that includes the names of all cities
of Italy.

It is suggested to register it under the same locale of the main Italian
dictionary with:

DICT it IT comuni

During the spell checking phase, if a word of comuni.dic is misspelled, OOo
underlines it as such, but when you right click on the word, the context menu
suggests words included in the main Italian dictionary only.

When comuni.it is used as main dictionary, OOo suggests the correct words
included in it.

This fact should show that when 2 dictionaries are used with the same
locale/affix file, OOo is able to handle the words of the second dictionary, but
not the automatic suggestions for the corrections of a misspelled word.
Comment 1 luctur 2002-09-12 09:31:16 UTC
It seems there is some problems with IZ and I'm not able to add
attachments...

However you can find comuni.dic included in the package you find here:

http://prdownloads.sourceforge.net/ooodocs/it_IT_1.6.zip?download
Comment 2 khendricks 2002-09-12 14:19:15 UTC
Hi, 
 
Two things. 
 
1. Every dictionary must have its own properly named affix file. 
Differnt dictionaries even for the same locale may have or use 
differnt encoding, use differnt TRY strings, etc. 
 
So if you have a comuni.dic you need a comuni.aff file with the 
proper settings. 
 
2. Order is important when it comes to suggestions.  Put the main 
dictioanry first and any other additional dictionaries second.  If a 
word is mispelled in both, it tries to generate suggestions from the 
main (first) dictionary.  If suggestions are found and they exceed 
some threashold (I have to see the code to remember the threshhold) 
suggestions from secondary dictionaries are not requested since the 
most common suggestions from the main dictioanry are most often 
right.  If fewer than the threshold suggestions are found after 
looking through the main dictionary, then suggestions are requested 
for the additional or sub dictionaries. 
 
I can change the threshold to something higher but it will slow down 
spellchecking for systems with lots of dictioanries. 
 
The threshhold might be as low as 1 now but I could easily raise 
that to 2 or 5 if that makes sense. 
 
Kevin 
 
 
You can control the order 
Comment 3 khendricks 2002-09-12 14:19:38 UTC
Hi, 
 
Two things. 
 
1. Every dictionary must have its own properly named affix file. 
Differnt dictionaries even for the same locale may have or use 
differnt encoding, use differnt TRY strings, etc. 
 
So if you have a comuni.dic you need a comuni.aff file with the 
proper settings. 
 
2. Order is important when it comes to suggestions.  Put the main 
dictioanry first and any other additional dictionaries second.  If a 
word is mispelled in both, it tries to generate suggestions from the 
main (first) dictionary.  If suggestions are found and they exceed 
some threashold (I have to see the code to remember the threshhold) 
suggestions from secondary dictionaries are not requested since the 
most common suggestions from the main dictioanry are most often 
right.  If fewer than the threshold suggestions are found after 
looking through the main dictionary, then suggestions are requested 
for the additional or sub dictionaries. 
 
I can change the threshold to something higher but it will slow down 
spellchecking for systems with lots of dictioanries. 
 
The threshhold might be as low as 1 now but I could easily raise 
that to 2 or 5 if that makes sense. 
 
Kevin 
 
 
You can control the order 
Comment 4 luctur 2002-09-13 10:56:26 UTC
Hi,

I've tested the threshold and it seems to be set to 1 because only the
second dictionary words that have no suggestions in the first one are
suggested correctly in the context menu. So, you should really raise
the threshold to 5 (?) if possible.
Comment 5 khendricks 2002-10-05 15:41:49 UTC
Hi, 
 
Okay, I will change the code to raise the threshhold. 
 
I will post here when the change is done. 
 
Kevin 
 
Comment 6 khendricks 2002-10-05 16:19:10 UTC
Hi, 
 
I decided to skip the threshhold completely sinc eit is arbitrary.  
I will now return all suggestions from all dictionaries registered 
for that locale. 
 
The implications for the dictionary maker is to make sure if they 
have multiple dictionaries registered for that locale that the 
intersection of the words in those dictionaries is 0 (i.e. they do 
not have any words in common).  This should not be an issue since 
there is no reason to have two dictionaries with the exact same 
words (it wastes memory, time, cycles, etc).  In the worst case, if 
the dictioanries do overlap, you may get duplicate suggestions (the 
same suggestion twice (once from each dictionary it appears in). 
This is of course not fatal!  ;-) 
 
I will test this change and then commit it to the tree.  It should 
appear in the next release after 643. 
 
Thanks, 
 
Kevin 
 
Comment 7 khendricks 2002-10-31 19:35:26 UTC
this is fixed in the latest OO643C lngucomponet.

Thanks,

Kevin
Comment 8 ace_dent 2008-05-17 21:54:45 UTC
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Andrew
 
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 9 ace_dent 2008-05-17 23:59:50 UTC
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew