Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: rfc2047.el bug?
Date: Thu, 11 Sep 2003 10:34:46 +0900	[thread overview]
Message-ID: <b9y3cf46rbd.fsf@jpl.org> (raw)
In-Reply-To: <m3znhcxili.fsf@defun.localdomain>

>>>>> In <m3znhcxili.fsf@defun.localdomain>
>>>>>	Jesper Harder <harder@myrealbox.com> wrote:

> Katsumi Yamaoka <yamaoka@jpl.org> writes:

>> Gnus sometimes encodes a Japanese-English mixture text to the
>> line length exceeding 76 characters.  For example:

[...]

> I've checked in a fix.

Thanks!  It fixes a problem when encoding at least Japanese text.
However, the FLIM's encoder is still high quality overwhelmingly.
We can use it for Gnus as follows:

(eval-after-load "mail-parse"
  '(progn
     (defalias 'mail-encode-encoded-word-buffer
       (lambda nil
	 (require 'eword-encode)
	 (mime-encode-header-in-buffer t)))
;;     (defadvice eword-encode-text (after downcase-charset activate)
;;       "Convert charset and encoding strings to lower case."
;;       (require 'eword-decode)
;;       (if (and ad-return-value
;;		(string-match eword-encoded-word-regexp
;;			      ad-return-value))
;;	   (setq ad-return-value
;;		 (concat
;;		  (downcase (substring ad-return-value
;;				       0 (match-beginning 4)))
;;		  (substring ad-return-value
;;			     (match-beginning 4))))))
     ))

P.S.
Please don't use smtpmail.el included in the FLIM package.  It
is slightly incompatible with the Emacs version of smtpmail.el.
I've made a proposal to remove it from the package, but there's
no response from the authors.
-- 
Katsumi Yamaoka <yamaoka@jpl.org>
;; I'm now renewing the "multiple message frames" suit. :)



      reply	other threads:[~2003-09-11  1:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10  4:29 Katsumi Yamaoka
2003-09-11  0:40 ` Jesper Harder
2003-09-11  1:34   ` Katsumi Yamaoka [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=b9y3cf46rbd.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    /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).