From: Eli Zaretskii <eliz@gnu.org>
To: Dmitri Paduchikh <dpaduchikh@gmail.com>
Cc: 24435@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#24435: 25.1; Problem using Hunspell
Date: Wed, 14 Sep 2016 19:57:10 +0300 [thread overview]
Message-ID: <8360py8lnd.fsf@gnu.org> (raw)
In-Reply-To: <8760pyzeam.fsf@gmail.com> (message from Dmitri Paduchikh on Wed, 14 Sep 2016 20:33:53 +0500)
> From: Dmitri Paduchikh <dpaduchikh@gmail.com>
> Date: Wed, 14 Sep 2016 20:33:53 +0500
> Cc: 24435@debbugs.gnu.org
>
> > I guess older Hunspell versions printed a different string. Does it
> > work if you change the regexp to
>
> > "\\(?:(but really \\)?Hunspell \\([0-9]+\\.[0-9\\.-]+\\)?)?"
>
> Sadly, it does not. The immediate cause of this error message is that
> regexp for ispell-program-version matches the Hunspell output. Then the
> corresponding check for Ispell version produces this error. The change
> shown below makes the version check pass, but another problem appears:
>
> | Starting new Ispell process hunspell with ru_RU dictionary...
> | ispell-phaf: No matching entry for ru_RU in ‘ispell-hunspell-dict-paths-alist’.
> | (ispell-parse-hunspell-affix-file)
>
> It seems that Hunspell itself does not have any difficulty locating the
> dictionary.
>
> $ hunspell -a -d ru_RU
> Hunspell 1.4.0
> проверкаа
> & проверкаа 3 0: проверка, проверкам, проверках
What does your Hunspell output when invoked thus:
$ hunspell -D
It should output all the dictionaries it has available -- that is what
ispell.el expects. It was a long-standing bug in Hunspell that (some
versions of) it didn't, so I'm guessing that bug is still not fixed.
Look in their bug database for a patch, apply it, rebuild Hunspell,
and it should work (unless my guess is wrong and some other factor is
at work here).
> Below is the change I made to work arround the version check.
Thanks, but I think this part is too drastic:
> - (if (ispell-check-minver ispell0-minver ispell-program-version)
> - (or (ispell-check-minver ispell-minver ispell-program-version)
> - (setq ispell-offset 0))
> - (error "%s release %s or greater is required"
> - ispell-program-name
> - ispell-minver))
> + (cond ((or (null ispell-program-version)
> + (ispell-check-minver ispell-minver ispell-program-version)))
> + ((ispell-check-minver ispell0-minver ispell-program-version)
> + (setq ispell-offset 0))
> + (:else (error "%s release %s or greater is required"
> + ispell-program-name
> + ispell-minver)))
We cannot give up the test of ispell-program-version. I suggest to do
this the other way around: if Hunspell reports version 1.4 or greater,
_then_ and only then skip the ispell-program-version test.
next prev parent reply other threads:[~2016-09-14 16:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 13:24 bug#24435: 25.1; Problem using Hunspell Dmitri Paduchikh
2016-09-14 13:46 ` Noam Postavsky
2016-09-14 15:33 ` Dmitri Paduchikh
2016-09-14 16:57 ` Eli Zaretskii [this message]
2016-09-14 17:44 ` Dmitri Paduchikh
2016-09-14 18:50 ` Eli Zaretskii
2016-09-14 20:10 ` Dmitri Paduchikh
2016-09-15 14:25 ` Eli Zaretskii
2016-09-15 15:22 ` Agustin Martin
2016-09-15 16:20 ` Eli Zaretskii
2016-09-15 17:36 ` Agustin Martin
2016-09-15 20:59 ` Dmitri Paduchikh
2016-09-16 6:29 ` Eli Zaretskii
2016-09-16 8:06 ` Dmitri Paduchikh
2016-09-16 8:34 ` Eli Zaretskii
2016-09-14 16:40 ` Eli Zaretskii
2016-09-15 13:41 ` Agustin Martin
2016-09-15 21:42 ` Dmitri Paduchikh
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=8360py8lnd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24435@debbugs.gnu.org \
--cc=dpaduchikh@gmail.com \
--cc=npostavs@users.sourceforge.net \
/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.