GNU bug report logs - #17742
Support for enchant?

Previous Next

Full log

Message #77 received at 17742 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Reuben Thomas <rrt <at> sc3d.org>
Cc: 17742 <at> debbugs.gnu.org, agustin6martin <at> gmail.com
Subject: Re: bug#17742: Acknowledgement (Support for enchant?)
Date: Tue, 20 Dec 2016 17:38:51 +0200

> From: Reuben Thomas <rrt <at> sc3d.org>
> Date: Mon, 19 Dec 2016 21:27:18 +0000
> Cc: 17742 <at> debbugs.gnu.org
> 
>     Also, there is no easy way to know which particular spellchecking engine is
>     being used. Enchant uses $(datadir)/enchant and ~/.enchant config files to
>     define preferences, but I see no way to make enchant tell which one is being
>     used. So, it is not easy to parse dictionary info.
> 
> ​enchant-lsmod lists the engine used for each dictionary, so this is certainly possible, as I said earlier. However, it's not a good idea, I think, to directly search for dictionary files and parse them, because this breaks the abstraction of using the binary and/or library

Emacs should cater to user expectations before it caters to
abstractions, IMO.  It is good to use abstractions, but if an
abstraction cannot support some useful feature, it should take a back
seat, and we should implement the feature based on lower-level
infrastructure.

In this case, using enchant-lsmod to figure out the engine, and then
using the existing code in ispell.el that supports that engine is an
okay solution when Enchant itself cannot provide the information we
need.

Of course, if/when Enchant provides the means to get at the
information we need, we should switch to using those means.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.