unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitri Paduchikh <dpaduchikh@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24435@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#24435: 25.1; Problem using Hunspell
Date: Wed, 14 Sep 2016 22:44:18 +0500	[thread overview]
Message-ID: <871t0mz899.fsf@gmail.com> (raw)
In-Reply-To: <8360py8lnd.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 14 Sep 2016 19:57:10 +0300")

Hello,

Eli Zaretskii <eliz@gnu.org> wrote:

>> | 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

$ hunspell -D < /dev/null
Hunspell 1.4.0
$ hunspell -a -D < /dev/null
SEARCH PATH:
.::/usr/share/hunspell:/usr/share/myspell:/usr/share/myspell/dicts:/Library/Spelling:/home/dmai/.openoffice.org/3/user/wordbook:.openoffice.org2/user/wordbook:.openoffice.org2.0/user/wordbook:Library/Spelling:/opt/openoffice.org/basis3.0/share/dict/ooo:/usr/lib/openoffice.org/basis3.0/share/dict/ooo:/opt/openoffice.org2.4/share/dict/ooo:/usr/lib/openoffice.org2.4/share/dict/ooo:/opt/openoffice.org2.3/share/dict/ooo:/usr/lib/openoffice.org2.3/share/dict/ooo:/opt/openoffice.org2.2/share/dict/ooo:/usr/lib/openoffice.org2.2/share/dict/ooo:/opt/openoffice.org2.1/share/dict/ooo:/usr/lib/openoffice.org2.1/share/dict/ooo:/opt/openoffice.org2.0/share/dict/ooo:/usr/lib/openoffice.org2.0/share/dict/ooo
AVAILABLE DICTIONARIES (path is not mandatory for -d option):
/usr/share/hunspell/ru_RU
/usr/share/hunspell/en_NG
/usr/share/hunspell/en_PH
/usr/share/hunspell/en_DK
/usr/share/hunspell/en_NZ
/usr/share/hunspell/en_BS
/usr/share/hunspell/en_AU
/usr/share/hunspell/en_IE
/usr/share/hunspell/en_GB-large
/usr/share/hunspell/en_BW
/usr/share/hunspell/en_US
/usr/share/hunspell/en_CA
/usr/share/hunspell/en_HK
/usr/share/hunspell/en_NA
/usr/share/hunspell/en_GH
/usr/share/hunspell/en_BZ
/usr/share/hunspell/en_SG
/usr/share/hunspell/en_GB
/usr/share/hunspell/en_ZW
/usr/share/hunspell/en_TT
/usr/share/hunspell/en_ZA
/usr/share/hunspell/en_IN
/usr/share/hunspell/en_AG
/usr/share/hunspell/en_JM
/usr/share/myspell/dicts/ru_RU
/usr/share/myspell/dicts/en_NG
/usr/share/myspell/dicts/en_PH
/usr/share/myspell/dicts/en_DK
/usr/share/myspell/dicts/en_NZ
/usr/share/myspell/dicts/en_BS
/usr/share/myspell/dicts/en_AU
/usr/share/myspell/dicts/en_IE
/usr/share/myspell/dicts/en_GB-large
/usr/share/myspell/dicts/en_BW
/usr/share/myspell/dicts/en_US
/usr/share/myspell/dicts/en_CA
/usr/share/myspell/dicts/en_HK
/usr/share/myspell/dicts/en_NA
/usr/share/myspell/dicts/en_GH
/usr/share/myspell/dicts/en_BZ
/usr/share/myspell/dicts/en_SG
/usr/share/myspell/dicts/en_GB
/usr/share/myspell/dicts/en_ZW
/usr/share/myspell/dicts/en_TT
/usr/share/myspell/dicts/en_ZA
/usr/share/myspell/dicts/en_IN
/usr/share/myspell/dicts/en_AG
/usr/share/myspell/dicts/en_JM
LOADED DICTIONARY:
/usr/share/hunspell/ru_RU.aff
/usr/share/hunspell/ru_RU.dic
Hunspell 1.4.0
$ 

The information about dictionaries is output to stderr, and the version
string - to stdout. I have added -a to ispell-call-process inside
ispell-find-hunspell-dictionaries, re-customized ispell-program-name
(since ispell-find-hunspell-dictionaries seems to be called through its
customization setter), and the error with missing dictionaries
disappeared. Now when I try to check some word, after waiting for
several seconds I get this message:

| Starting new Ispell process hunspell with ru_RU dictionary...
| Hunspell 1.4.0 (ispell-init-process)

Subsequent attempts give such result:

| Checking spelling of ВПЕРЁД...
| Error checking word ВПЕРЁД using hunspell with ru_RU dictionary

The word seems to pass spellcheck using CLI interface.

$ echo вперёд | hunspell -a -d ru_RU
Hunspell 1.4.0
*

$ 

Best regards
Dmitri Paduchikh





  reply	other threads:[~2016-09-14 17:44 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
2016-09-14 17:44       ` Dmitri Paduchikh [this message]
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

  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=871t0mz899.fsf@gmail.com \
    --to=dpaduchikh@gmail.com \
    --cc=24435@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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 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).