retitle 337687 Please improve README.emacs for ispell+accented characters 
customized entries
thanks

On Sat, Nov 05, 2005 at 08:24:04PM +0100, Norbert Preining wrote:
> I am having a hard time to get ispell in emacs to check words containing
> umlauts and accented characters.
> 
> I tried the following (according to README.emacs):
> 
> I added a new dictionary entry to ispell-local-dictionary-alist using
> customize:
> 
> (custom-set-variables
>   '(ispell-local-dictionary-alist 
>      (quote (("american8" "[A-ZÄÖÜäöüß]" "[^A-ZÄÖÜäöüß]" "[']" nil 
>              ("-B" "-d" "american") "~latin1" iso-8859-1)))))
> 
> (Besides this my test .emacs is empty!)
> 
> Which I though should work.
> 
> Then I selected the american8 dictionary and wanted to check 
>       Gödel
> and got
>       "Ispell and its process have different character maps."
> 
> How can I get ispell/emacs to check this correctly?

Hi, Norbert and David

I am afraid that is a limitation of current Debian ispell,

-----------------------
$ echo "Gödel" > test.data
$ cat test.data | ispell -l -d american
del
-----------------------

That is what triggers the error message, and will happen when a word with
characters not in ispell declared chars (in the aff file) is spellchecked. If
the offending char is not in the Casechars/Not-Casechars sections for
ispell.el will be treated as a boundary char and there will be no
complain about that (although sometimes might derive in misalignment
errors).

The example in README.emacs was originally for aspell (and arised after
#299725), although unfortunately I did not explicitely mention that. I
will add specific info about that.

The proper fix would be to update ispell to the most recent version, whose
american dict allows in its aff file much more 8 bit characters, but that is
definitely an ispell issue. The presence of a newer ispell has already been
reported (#306604), so I am sending a followup there. I will close the
dictionaries-common part of this bug report once I improve documentation.
I am not cloning it and merging with #306604, but feel free to do that
by yourself.

-- 
Agustin

Reply via email to