Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Editing UTF-8 mail messages
Date: Mon, 14 Oct 2002 06:05:08 +0200	[thread overview]
Message-ID: <m37kglsm17.fsf@defun.localdomain> (raw)
In-Reply-To: <m3elavlzjg.fsf@defun.localdomain> (Jesper Harder's message of "Sun, 13 Oct 2002 06:42:59 +0200")

Jesper Harder <harder@ifa.au.dk> writes:

> 1. When you do a plain `e' Gnus, mangles the encoding.  This seems to be
>    one of the usual MULE-related \201-problems.
>
>    In this case it's caused by `mm-get-part' (in mm-decode.el), which
>    uses the macro `mm-with-unibyte-current-buffer-mule4'.  This macro
>    does *not* make the buffer unibyte temporarily.
>
>    I don't understand the point of `mm-w-u-c-b-mule4' -- it doesn't
>    work.  Why is it ever used?  I suspect that the use of it in several
>    places could be causing some of the occasional \201-problems.
>
> -	      (mm-with-unibyte-current-buffer-mule4
> +	      (mm-with-unibyte-current-buffer

Hmm, it might not be the right fix after all.  

It does fix the utf-8 editing problem, and I think also another problem
that someone reported in gnu.emacs.gnus about utf-8 format=flowed
messages being mangled.

*But* it introduces \201's in message/rfc822-forwarding of non-ascii
messages :-(  

Hmm, is the " *mm*"-buffer associated with a MIME-handle supposed to be
unibyte or multibyte?




      reply	other threads:[~2002-10-14  4:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 15:49 Karl Eichwalder
2002-10-13  4:42 ` Jesper Harder
2002-10-14  4:05   ` Jesper Harder [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m37kglsm17.fsf@defun.localdomain \
    --to=harder@ifa.au.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).