vm team mailing list archive

[terrycojones <terry@xxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 430521 ***
    https://bugs.launchpad.net/bugs/430521

Setting  vm-mime-8bit-composition-charset to "utf-8" has no effect for
me. I'm using VM 7.19 on emacs 23.1.50.1 running on Hardy. If I toggle
input mode to latin-9-prefix and enter a 'i for an i acute and send
mail, the outgoing message has

Content-Type: text/plain; charset=unknown

Terry

-- 
vm: sends garbled non-ASCII in default setup
https://bugs.launchpad.net/bugs/490018
You received this bug notification because you are a member of VM
development team, which is the registrant for VM (defunct) (via bug
430521).

Status in VM (View Mail) for Emacs: New
Status in “vm” package in Debian: Confirmed

Bug description:
Hi,

        [Please retain a CC to 508552-forwarded@xxxxxxxxxxxxxxx in order
        for the Debian bug tracking system to retain a record of your
        contribution] 

        This was reported by a Debian user.

        In VM's default setup messages containing non-ASCII characters
 are sent as "Content-Type: text/plain; charset=iso-2022-jp".  They look
 garbled in every MUA (Gnus, VM, Rmail, Icedove) I've tried.  If an
 iso-2022 encoding is used at all, at least "Content-Type: text/plain;
 charset=iso-2022-7bit" should be used, which would make the messages
 readable in Emacs-based MUAs.

        Note that this applies to messages sent in VM under emacs22,
 with emacs-snapshot the situation is even worse: all non-ASCII
 characters silently disappear when the message is sent!

        This can be worked around by setting
 vm-mime-8bit-composition-charset to "utf-8" which makes VM send
 messages as "Content-Type: text/plain; charset=utf-8", although the
 docstring for vm-mime-8bit-composition-charset wrongly claims that this
 variable has no effect.

        manoj