On 2005-11-13 at 18:55 +0100 Daniel Naber sent off:
On the other hand, why keep myspell at all if hunspell is like myspell + additional features?
well, there might arise problems with hunspell (e.g. some backward compatibility issues) and one might want to fall back to myspell. Or You might want to use hunspell and myspell side by side (I would like to, but maybe I'm a special case ;-) ). Anyway - I would like to see hunspell not use the dictionaries defined by "DICT" as default but those defined by something like "DICT_HUNSPELL". There might come other spellcheck engines in the future and having a not so generic name like "DICT" which doesn't say *which* spellcheck engine's DICT this is, is not very clean.
How about this: as "DICT" is from the beginning a "variable" for myspell dictionaries and hunspell should also be able to use this ones, hunspell should first look for "DICT_HUNSPELL" entries and if it doesn't find any, it should use "DICT" entries.
This way, we have no naming problem in dictionary.lst when there comes a "foospell" engine. It's dictinoaries can be named with "DICT_FOOSPELL".
BjoernPS: I would propose the same engine-specific dictionary.lst entries for thesauri and hyphenators too as there may be more than one and people might want to switch without editing the dictionary.lst file.
pgpnWrADa0Sfp.pgp
Description: PGP signature
