On Sat, Feb 12, 2005 at 06:58:13PM +0100, Remi Vanicat wrote: > Package: dictionaries-common > Version: 0.24.7 > Severity: normal > > Hello, > > I'm the maintainer of the aspell-fr package, and so I'm testing the > dictionaries-common registration feature. And I've found what I believe > is a bug: If I install the iamerican debian package, I lose the > aspell-fr binding. And if I install for example ifrench-gut package, > I've the french binding back, but not all the one I've put in the > aspell-fr package (their are several dictionary, for several variant > of the french language, and several size for the dictionary). >
Hello, ispell.el checks only for ispell dicts at /usr/lib/ispell, not for aspell dicts, so it returns as valid-dictionary-list only those that have an ispell equivalent hash installed. However, if you set ispell-program-name to aspell and use something like ; Local Variables: ; mode: text ; ispell-local-dictionary: "galego-minimos" ; End: (Put your aspell dict there) without having the associated ispell dict installed it will work, and using the casechars... good values, not those taken from the default, and after this the entry will be available for ispell-change-dictionary. If an ispell dict having the same hash name is installed you will see all the values sharing that hash name (or the value given with --master) when calling to ispell-change-dictionary, as well as when using the pop-up menus. This is not related to the registration mechanism, but with ispell.el itself. I am considering the possibility of manually feeding the list of installed ispell/aspell dicts to valid-dictionary-list, so all are seen, but at least for the pop up menus I would like to somehow show whether they are available for ispell, aspell or both, so anybody selecting an entry know if that will work for aspell or for ispell or for both. Otherwise this might be confusing if they select a language and ispell.el complains that e.g. /usr/lib/ispell/lang.hash is not available because aspell dict is installed for that value. The ideal thing should be to select ispell or aspell depending of the user preferences and the selected dictionary, so all ispell-change-dictionary entries are valid, some of them using ispell and some others using aspell, and all that is automagically handled at spellcheck call. Please let me know if this is what is happening in your system, or is something different. Cheers, -- Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
