Something about charsets is broken in message mode

[Frank Schmitt <usereplyto@Frank-Schmitt.net>]

Hello

After I switched from Windows to Linux, I have some difficulties in
message mode which I think indicate bugs.

First of all flyspell: Flyspell and ispell work in every Emacs buffer
but not when I'm in message mode. There words containing Umlauts like
"über" aren't recognized. I can't even search for words containing
Umlauts, Emacs says "no match" as well as the word is definitely
there. In other buffers, this is no problem too.

I use a GTK-CVS-Head-Emacs from late November and todays CVS Gnus. 
$LANG is set to en_US.ISO8859-15 language environment isn't set by me,
but if I chose ISO-latin-9 it doesn't make a difference.

An other strange thing: If I say C-h v buffer-file-coding-system in a
message buffer the value is emacs-mule-dos as well as I'm on a Unix
system. Could the reason be, that I use my old mail folders from
Windows?

BTW: Outgoing mails and news are encoded in UTF-8 as I say 
(setq mm-coding-system-priorities '(mule-utf-8)) in .gnus. Wouldn't it
make much more sense to save drafts in Unicode, too?

I can fix the flyspell problem by saying
(require 'ispell)
(add-to-list 'ispell-local-dictionary-alist
      '("ndeutsch8-15"
        "[a-zA-Z\xf44\xf56\xf5c\xf5f\xf64\xf76\xf7c]"
        "[^a-zA-Z\xf44\xf56\xf5c\xf5f\xf64\xf76\xf7c]"
        "[']" t
        ("-C" "-d" "ndeutsch")
        "~latin1" iso-8859-15))
in .gnus but this is only a dirty hack and doesn't fix the other
problems described above.

-- 
Did you ever realize how much text fits in eighty columns? If you now consider
that a signature usually consists of up to four lines, this gives you enough
space to spread a tremendous amount of information with your messages. So seize
this opportunity and don't waste your signature with bullshit nobody will read.