all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: 17742@debbugs.gnu.org
Subject: bug#17742: Support for enchant?
Date: Tue, 10 Jun 2014 01:01:24 +0100	[thread overview]
Message-ID: <CAOnWdogPF5AJ2RU1pFXB2GhAGdR4sx5Kx1gatm_vF=2cEg3cJw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]

It would be good if Emacs supported the Enchant multi-back-end spelling
engine wrapper, as this allows users to configure spelling preferences more
flexibly than Emacs (in particular, to use different spell-checking engines
for different languages), and the configuration works for programs other
than Emacs.

It seems that it would be pretty trivial to add, since Emacs already works
fine (since 2007) if you set ispell-program-name to /usr/bin/enchant.

Enchant supports UTF-8 (and only UTF-8) as an encoding, so for optimum
functionality, I guess support would need to be added to
ispell-encoding8-command (though since this is enchant's only mode of
operation, it's unclear that anything needs to be done).

In a wider GNU context, the GNU aspell developer wrote a few years ago: "I
believe Aspell future depends on making Enchant the system spell
checker."[1] Enchant itself seems to be stable, portable, and support a
wide range of spelling checker engines, including all those that Emacs
already supports; it would be great longer-term to be able to simplify
ispell.el by requiring Enchant, and thereby being able to rely on its UTF-8
support and single set of simple options.

[1] http://aspell.net/

-- 
http://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1459 bytes --]

             reply	other threads:[~2014-06-10  0:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10  0:01 Reuben Thomas [this message]
2014-09-15 11:06 ` bug#17742: Limitations of enchant Reuben Thomas
2016-12-02  0:15   ` Reuben Thomas
     [not found] ` <handler.17742.B.140235850213377.ack@debbugs.gnu.org>
2016-12-05 21:41   ` bug#17742: Acknowledgement (Support for enchant?) Reuben Thomas
2016-12-06 15:55     ` Eli Zaretskii
2016-12-06 15:56       ` Reuben Thomas
2016-12-13  0:53         ` Reuben Thomas
2016-12-13 16:37           ` Eli Zaretskii
2016-12-13 18:26             ` Reuben Thomas
2016-12-13 18:54               ` Eli Zaretskii
2016-12-13 21:17                 ` Reuben Thomas
2016-12-13 21:30                   ` Reuben Thomas
2016-12-14 15:42                   ` Eli Zaretskii
2016-12-15 12:36                     ` Reuben Thomas
2016-12-18 23:39                 ` Reuben Thomas
2016-12-19  1:02                   ` Reuben Thomas
2016-12-19 12:41                     ` Reuben Thomas
2016-12-19 16:01                   ` Eli Zaretskii
2016-12-19 17:37                     ` Agustin Martin
2016-12-19 18:09                       ` Eli Zaretskii
2016-12-19 21:21                         ` Reuben Thomas
2016-12-19 21:27                       ` Reuben Thomas
2016-12-20 15:38                         ` Eli Zaretskii
2016-12-19 21:47                     ` Reuben Thomas
2016-12-19 22:04                       ` Reuben Thomas
2016-12-20 15:40                         ` Eli Zaretskii
2016-12-20 15:40                       ` Eli Zaretskii
2016-12-20 21:43                         ` Reuben Thomas
2016-12-21 17:13                           ` Eli Zaretskii
2016-12-21 17:32                             ` Reuben Thomas
2017-08-09 11:35                               ` Reuben Thomas
2017-08-18  8:54                                 ` Eli Zaretskii
2017-08-20 13:02                                   ` Reuben Thomas
2017-08-20 14:42                                     ` Eli Zaretskii
2017-08-20 14:50                                       ` Reuben Thomas
2017-08-20 19:34                                         ` Eli Zaretskii
2017-08-20 20:36                                           ` Reuben Thomas
2017-08-20 14:50 ` bug#17742: Reuben Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOnWdogPF5AJ2RU1pFXB2GhAGdR4sx5Kx1gatm_vF=2cEg3cJw@mail.gmail.com' \
    --to=rrt@sc3d.org \
    --cc=17742@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.