Re: pop3.el broken

[Katsumi Yamaoka <yamaoka@jpl.org>]

>>>>> In <m3sn73agyk.fsf@peorth.gweep.net> 
>>>>>	Stainless Steel Rat <ratinox@peorth.gweep.net> wrote:

> * Katsumi Yamaoka <yamaoka@jpl.org>  on Wed, 13 Mar 2002
> | I found that the difference is caused by Mule-UCS.  I'll
> | consider how to fix the problem.

> If you are looking at changing pop3.el because something is broken, stop.

Ok, I agree.

> If it does not fit in the pop3-movemail function then the problem is
> somewhere not in pop3.el.  I tried making the process buffer unibyte four
> years ago.  It will not work.  The MULE environment will force it multibyte
> anyway (see the recent batch of \201 sightings).

> The buffer must remain multibyte in a MULE environment, and must have
> coding-system 'binary.  That is the only way it works.

> The bug you've found is in MULE-UCS, not pop3.el.

I'm afraid so it is.  I've sent a question to the mule-ja list
this morning (in Japan).  Now I'm using the following advice for
the temporary repairs.

(defadvice md5 (before treat-7bit-chars-as-unibyte activate)
  "Treat 7bit chars as unibyte."
  (if (string-match "^[\000-\177]+" (ad-get-arg 0))
      (ad-set-arg 0 (string-as-unibyte (ad-get-arg 0)))))
-- 
Katsumi Yamaoka <yamaoka@jpl.org>