all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17742@debbugs.gnu.org
Subject: bug#17742: Acknowledgement (Support for enchant?)
Date: Mon, 19 Dec 2016 22:04:55 +0000	[thread overview]
Message-ID: <CAOnWdoj8EY5nBHG8EUT+c9+pG5S6u7g7tvDLb+ZqT1uGj0M1CA@mail.gmail.com> (raw)
In-Reply-To: <CAOnWdoinKZc9wK-KZpPVBjsGcG1Bphvt7PEu49S55mGDnoJcmg@mail.gmail.com>

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

On 19 December 2016 at 21:47, Reuben Thomas <rrt@sc3d.org> wrote:

>
> ​Having discovered that Aspell does not provide this information (I
> checked again, and ispell-aspell-find-dictionary does not find this
> information in the dictionaries, except for limited information about
> otherchars; for casechars and not-casechars it defaults to [:alpha:]), I
> shall investigate with the hunspell maintainers.​
>

​Hunspell has an open bug to export an API to get the casechars (which
hunspell calls "WORDCHARS"):

https://github.com/hunspell/hunspell/issues/282

It has been added to the 2.0 milestone. So it seems there is light at the
end of this particular tunnel.

I've added a comment that it would be good to have a way to get this
information from the hunspell binary too.

My suggestion on how to proceed would therefore be:

1. Assuming my patches to enchant are accepted sooner rather than later,
and there's a minor Enchant release soon, then accept an initial
implementation of Enchant support in Emacs with a fixed casechars value.
This is no worse than for Aspell.

1a. If someone wants to add a way for Emacs to parse hunspell dictionaries
when used via Enchant, that's fine by me as a temporary workaround.

2. When hunspell 2 is released, hopefully there will be an official channel
for Emacs to get this information. Any workaround introduced as per 1a
above would now be more solid.

3. Once one of Enchant's supported engines has an official way to get this
information, then it's a good time to add an API to Enchant too (and
support in the standalone binary).

Overall, there's no hurry. We have precise casechars for hunspell
dictionaries today (though as I mentioned elsewhere, there may still be
problems with using them). Enchant support for now is useful for the
spelling checkers it supports that Emacs does not; obviously, Emacs's
direct hunspell support is better for now than via Enchant. It would be
nice to fix that eventually and use only Enchant, but there's no need to
rush.

-- 
http://rrt.sc3d.org

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

  reply	other threads:[~2016-12-19 22:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10  0:01 bug#17742: Support for enchant? Reuben Thomas
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 [this message]
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=CAOnWdoj8EY5nBHG8EUT+c9+pG5S6u7g7tvDLb+ZqT1uGj0M1CA@mail.gmail.com \
    --to=rrt@sc3d.org \
    --cc=17742@debbugs.gnu.org \
    --cc=eliz@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.