🚀 go-pugleaf

Hi Robert,

I'm pretty sure emacs 22 would do the job properly :) but as I'm rather
fond of that fancy xft support that comes along with 23, I'm still
reluctant to switch...but who knows...

As for the C-c C-e that's a real suprise. Here, the buffer before typing
C-c C-e:
To: tommy@localhost
Subject: test
X-Mailer: VM 8.1.0 under Emacs 23.0.0.1 (x86_64-unknown-linux-gnu)
FCC: ~/.myMail/SentMail
--text follows this line--
�ml��t�

Now, after encoding:
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
To: tommy@localhost
Subject: test
X-Mailer: VM 8.1.0 under Emacs 23.0.0.1 (x86_64-unknown-linux-gnu)
FCC: ~/.myMail/SentMail
--text follows this line--
 ml  t

And encoding in iso-2022-jp is very likely not what I want :) I guess
"jp" stand for Japanese?!

Thanks a lot...
f�r die Hilfe und dass Du VM weitermachst!!!

Gr��e,
	Tommy


newsspam5REMOVETHIS@robf.de wrote:
> Tommy Berndt <tommy@nowhere.net> writes:
>> I've just compiled vm-8.1.0-devo-478 with my brand new emacs 23.0.0.1.
>> Now I observe that any umlauts (I guess any other unicode or multi-byte
>> chars are affected as well) are lost when I send a mail - either a new
>> one, a reply, or forwarding.
>> Anyone an idea? Is it vm or is it the multi-byte handling of the new
>> emacs which is still alpha(!)
> 
> They should not be lost, please try it with Emacs 22.
> 
> You should check how Vm has encoded the message, i.e. compose a
> message with some of those chars and check how it is encoded by
> VM, i.e. C-c C-e (vm-mime-encode-composition).
> 
> Check the Content-Type: header and the text.
> 
> Robert.

-- 
_____________________________________________________________________
                                            Aberglaube bringt Ungl�