unofficial mirror of bug-gnu-emacs@gnu.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: Tue, 13 Dec 2016 18:26:43 +0000	[thread overview]
Message-ID: <CAOnWdojHC5PBO_ueNBtSCBCkWKTbMUJZbrW84N4XV7fZVKQvmg@mail.gmail.com> (raw)
In-Reply-To: <83bmwfbxaf.fsf@gnu.org>

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

On 13 December 2016 at 16:37, Eli Zaretskii <eliz@gnu.org> wrote:

>
> I'm sorry, I don't think this is good enough for any language but
> English.  I looked at a few Hunspell dictionaries I have, and almost
> all of them have some non-[:alpha:] characters in what becomes
> CASECHARS when ispell.el sets up itself for that dictionary.  So this
> seems to be really important for correct spell-checking of almost any
> language.  Moreover, these settings must be in sync with the words in
> the dictionary, so it isn't just some general setting determined by
> the dictionary's language, it must come from the dictionary or its
> authors.
>

​I agree, this is something that seems to be lacking in Enchant.​


> I understand that Enchant doesn't yet support these features, but in
> that case we must provide our users with some way of customizing these
> settings, we cannot silently use defaults that are most probably
> inappropriate, even if they are 90% correct.
>

​The way to customize it is surely the same as currently, namely​ to
customize ispell-dictionary-alist?​


> Do the dictionaries used by Enchant really fail to provide this
> information?  Aren't they Aspell dictionaries or similar?
>

​​Enchant has no dictionaries of its own, it's just a proxy for hunspell,
aspell &c. So, as I said before, it would be possible to find out which
back-end is being used for a particular dictionary, and then to try to use
the existing ispell.el code to scan for that dictionary. However, this is
not an ideal solution, because it is going "behind Enchant's back".

Given that even management of personal word lists needs a patch to Enchant,
it seems to me better to first try to engage with the Enchant maintainers
on this. There's also one obvious question, namely, what do other Enchant
users do? Enchant is used in Abiword (free word processor), Pidgin (free IM
client) etc. So, I shall look into this.

However, I think that this patch can be installed anyway, as out of the box
Enchant will never be used (as I have commented in the code, auto-detection
of Enchant is not safe until a new version is widespread, as unlike old
versions of ispell and aspell, a current version of Enchant is not merely
lacking functions, it is useless), and for some Emacs users, it could be
useful, as it allows access to spellcheckers currently unsupported by Emacs
(albeit, as you note, probably requiring customized dictionary setup).

-- 
http://rrt.sc3d.org

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

  reply	other threads:[~2016-12-13 18:26 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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=CAOnWdojHC5PBO_ueNBtSCBCkWKTbMUJZbrW84N4XV7fZVKQvmg@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).