[Top][All Lists]

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

Re: buffer-swap-text and multibyteness

From: Eli Zaretskii
Subject: Re: buffer-swap-text and multibyteness
Date: Tue, 24 Feb 2009 20:48:04 +0200

> From: Kenichi Handa <address@hidden>
> CC: address@hidden, address@hidden, address@hidden
> Date: Tue, 24 Feb 2009 17:09:45 +0900
> In article <address@hidden>, Eli Zaretskii <address@hidden> writes:
> > You are right, rmail-cease-edit was too naive in selecting the correct
> > encoding.
> > I think I fixed your use-case now, please try.  After base64 decoding
> > the Latin-1 text and manually decoding the text with
> > decode-coding-region, if buffer-file-coding-system cannot safely
> > encode the message, Emacs will ask you to select a safe encoding when
> > you type C-c C-c.  You can also set the correct encoding manually
> > before you type C-c C-c.  The charset= header is rewritten as needed,
> > as part of putting the modified message back into the message
> > collection buffer.
> Thank you, I confirmed that this problem is fixed.

Thanks for testing it.

Btw, while I worked on this, I discovered a strange problem with a
coding-system I never heard about before: iso-2022-jp-2.  (It was one
of the encodings select-safe-coding-system suggested for encoding the
text with both Japanese and Latin-1 characters.)  Whenever I used
iso-2022-jp-2 to encode the edited message back into the mbox buffer,
Emacs crashed inside GC.  Is something wrong with that coding-system?

reply via email to

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