Gnus development mailing list
 help / color / mirror / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: bsam@ipt.ru, handa@m17n.org, ding@gnus.org
Subject: Re: gnus: incorrect conversion of Subject and From field from utf-8 to koi8-r
Date: Wed, 19 Oct 2005 16:16:04 -0400	[thread overview]
Message-ID: <E1ESKM0-0002Z4-Im@fencepost.gnu.org> (raw)
In-Reply-To: <b4mfyqyjgbs.fsf@jpl.org> (message from Katsumi Yamaoka on Wed, 19 Oct 2005 13:12:07 +0900)

       Each 'encoded-word' MUST represent an integral number of characters.
       A multi-octet character may not be split across adjacent 'encoded-
       word's.

    It doesn't mean to prohibit to try to decode them though, and
    that Gnus does it would be nice.

I agree.  Maybe mailers should not generate this,
but if they do, it is better for Gnus to handle it right.

    BTW, I realized that that fix was insufficient.  For instance,
    it will display binary garbage if the charset specified in the
    encoded-word is unknown.  So, I will CVS commit the new code
    after a while.

Thank you in advance.



  reply	other threads:[~2005-10-19 20:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1EQHq4-0002rQ-EC@fencepost.gnu.org>
     [not found] ` <E1EQPSa-0006iC-00@etlken>
2005-10-14 16:51   ` Katsumi Yamaoka
2005-10-15  0:46     ` Kenichi Handa
2005-10-15  8:28       ` Katsumi Yamaoka
2005-10-15  8:50         ` Kenichi Handa
2005-10-15 10:06           ` Katsumi Yamaoka
2005-10-16  0:25             ` Kenichi Handa
2005-10-18 18:20             ` Boris Samorodov
2005-10-19  4:12               ` Katsumi Yamaoka
2005-10-19 20:16                 ` Richard M. Stallman [this message]
     [not found] <E1EQ6NU-000GJF-2s@bsam.ru>
2005-10-13 18:26 ` Reiner Steib

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=E1ESKM0-0002Z4-Im@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=bsam@ipt.ru \
    --cc=ding@gnus.org \
    --cc=handa@m17n.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).