[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [h-e-w] Can't open affix or dictionary flies

From: Eli Zaretskii
Subject: Re: [h-e-w] Can't open affix or dictionary flies
Date: Fri, 11 Jan 2013 12:45:40 +0200

> Date: Fri, 11 Jan 2013 10:11:31 +0100
> From: Oliver Jones <address@hidden>
> Cc: address@hidden
> I made sure the dictionary and affix files are saved in a place where 
> hunspell finds them (I 
> verified that by executing hunspell on the command line). I changed the text 
> in my init.el to:
> (setq ispell-dictionary-alist
>     '((nil ; default
>        "[a-zäöüßA-ZÄÖÜ]" "[^a-zäöüßA-ZÄÖÜ]" "[']" t
>        ("-d" "de_DE_frami") nil utf-8)
>       ("en_GB"
>        "[A-Za-z]" "[^A-Za-z]" "[']" nil
>        ("-d" "en_GB") nil utf-8)
>       ("de_DE_frami"
>        "[a-zäöüßA-ZÄÖÜ]" "[^a-zäöüßA-ZÄÖÜ]" "[']" t
>        ("-d" "de_DE_frami") nil utf-8)))
> (eval-after-load "ispell"
>      (progn
>        (setq ispell-dictionary "de_DE_frami"
>           ispell-extra-args '("-a" "-i" "utf-8") ; aspell doesn't understand 
> -i utf-8, hunspell 
> needs it
>           ispell-silently-savep t)))
> (setq ispell-program-name "C:\\Dokumente und Einstellungen\\ojones\\Eigene 
> Dateien\\hunspell-mingw-1.3.2-win32\\bin\\hunspell.exe")
> Now when I start ispell by M-x ispell there is no error message and I see an 
> ispell process 
> using M-x list-processes:
> Process: ispell
> Status:  run
> Buffer:  --
> TTY:     --
> Command: C:\Dokumente und Einstellungen\...\hunspell.exe -a  -d de_DE_frami 
> -i nil -a -i utf-8

That "-i nil" should not be there, you should try finding out where
did it come from.

> But it dosen't work as far as I can tell. No words are identified as
> misspelled (I included some for testing purpose).

If you go to some misspelled word and type "M-$", don't you see the
"*Choices*" buffer pop up with suggested corrections, and a prompt in
the echo area with a few keys to use to either correct or leave alone
the word?  If these two happen, then spell-checking does work.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]