From: Karl Kleinpaste <karl@justresearch.com>
Subject: p0.88 possible charset bug
Date: 17 Jun 1999 10:56:16 -0400 [thread overview]
Message-ID: <vxkemjac1v3.fsf@beaver.jprc.com> (raw)
On the xemacs-beta list, steve@xemacs.org posts a note whose headers
include...
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=ISO-2022-JP
Message-ID: <hpzlndjk376.fsf@miho.m17n.org>
X-Mailer: Gnus v5.6.45/XEmacs 21.2 - =?ISO-2022-JP?B?IhskQktPRUQbKEIi?=
The bulk of his message contains only 7-bit characters, but his
signature contains...
^[$BAkHV9f$rF~NO$7$F$/$@$5$$^[(B
Presumably, given Content-Type charset ISO-2022-JP, this signature
sequence should have been rendered in that charset, but it was not --
just the raw crud is displayed. However, I note that the X-Mailer
contains a legitimate charset sub-encoding, which is properly rendered
when headers are `t'oggled.
Is this an error on p0.88's part, or does the signature not need
charset treatment?
(I know quite a few folks on the ding list are also on xemacs-beta;
Message-Id is above, so you might take a look yourselves.)
next reply other threads:[~1999-06-17 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-17 14:56 Karl Kleinpaste [this message]
1999-06-17 16:18 ` Didier Verna
1999-06-17 17:07 ` Karl Kleinpaste
1999-06-26 4:10 ` Shenghuo ZHU
1999-06-28 15:20 ` Karl Kleinpaste
1999-06-29 12:35 ` Hrvoje Niksic
1999-06-29 6:22 ` Shenghuo ZHU
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=vxkemjac1v3.fsf@beaver.jprc.com \
--to=karl@justresearch.com \
/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).