Hi,
I designed it that way. That code is written and put into place by
me to support the components I either wrote (myspell and mythes) or
inherited (hyphenator). The reason you are confused is that there
really has never been another spellchecker, thesaurus or hyphenator
for OOo until now. I chose to use a dictionary.lst and its install
location and its format so that OOo had something that worked at
all. Now, Hunspell can take that code over since it will replace
MySpell as the "official" spellchecker of OOo but other non-official
components really should and will figure out how to let their own
components know what the users have installed and actually want to use.
My 2 cents,
Kevin
On Dec 24, 2005, at 3:43 AM, Bjoern JACKE wrote:
On 2005-12-23 at 21:07 -0500 Kevin B. Hendricks sent off:
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.
I think reality looks different - from the start dictionary.lst
contained hyphenation and thesaurus dictionaries. That
dictionary.lst is a myspell-only thing is realy new for me. Apart
from that a name with a very generic name like dictionary.lst at
such an exposted place like this would be expected by everyone to
be a generic config file not a myspell-specific one.
Cheers
Bjoern
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: dev-
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
