Hi,

The whole "dictionary.lst" mechanism is part of the spell checking component (ie. the MySpell spell checker). So another spell checking component need not and should not use the concept of "dictionary.lst" since that was developed for MySpell and MyThes components. It is being adopted for HunSpell since it is replacing MySpell. So an arabic or commerical or some other spell checker should not use MySpell dictionary.lst but should instead use some other method to allow users to install and update their dictionaries.

Also since old MySpell dictionaries will work just fine with Hunspell, and since dictionary authors that choose to use HunSpell specific features can simply name their dictionaries something else (en_US_hunspell for example), this really should not be an issue.

Again, the best solution is to get rid of Myspell as fast as possible (IMHO). Users of old OOo versions can simply install a properly compiled hunspell component if they want to use hunspell dictionaries.

My 2 cents,

Kevin



On Dec 23, 2005, at 5:44 PM, Bjoern JACKE wrote:

Hi!

On 2005-12-23 at 08:55 -0500 Kevin B. Hendricks sent off:
So IMHO, we should remove MySpell completely from the source tree when Hunspell is integrated.

That will remove the duplication and prevent confusion. Then we would have NO Myspell vs HunSpell issues in dictionary.lst

there will be confusion for dict downloaders who use older OOo versions (just supporting myspell) and dict downloaders who use newer OOo versions (using hunspell). At the time where dictionaries which will use hunspell specific features and there is no seperation of my/hunspell dicts, users of myspell OOo versions will not be happy anymore and download broken (for myspell useage) dictionaries ;-). Other spellcheck engines than my/hunspell which require other dictionaries will also require a dictionary.lst change to not mix up things completely. For example - how should an Arabic spellcheck engine's dictionary entries be distinguished from an Arabic hunspell dictionary? I hope a dictionary.lst change will come before hunspell will altually BE the default.

Cheers
Bjoern


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to