From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: Re: test message: broken content-type & 8-bit messages
Date: 10 Dec 1998 23:57:21 +0300 [thread overview]
Message-ID: <m31zm7zpe6.fsf@vvv.vsu.ru> (raw)
In-Reply-To: Michael Welsh Duggan's message of "Thu, 10 Dec 1998 20:31:57 GMT"
"MWD" == Michael Welsh Duggan writes:
>> btw, it would be nice to be able to force decoding for a given
>> charset for a non-multipart messages, too (in cases when charset
>> was specified incorrectly by a broken MUA). [for non-multipart
>> messages there are no buttons, and `i' is not working]
MWD> `C-u W M c' doesn't work?
Hmm [i did not know about `W M c']. Here is what i get:
* if the article is already decoded (maybe, wrongly), then pressing
`C-u W M c' and specifying another charset causes buggy
double-decoding (resulting in \214<8-bit-char> mess)
* to deal with the above [is it a bug?] i can do `C-u g' an article
before pressing `C-u W M c'.
* and most important, this does not work for the article which started
this thread: pressing `C-u W M c' and specifying any charset has no
effect at all --- an article remains unencoded (i.e. looks like
`\301\305\302...'). this is perhaps a bug.
Best regards, -- Vladimir.
prev parent reply other threads:[~1998-12-10 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-09 15:37 Vladimir Volovich
[not found] ` <5bk901z3lk.fsf@brandy.cs.rochester.edu>
[not found] ` <m367blnp7x.fsf@vvv.vsu.ru>
[not found] ` <5b90ghf956.fsf@brandy.cs.rochester.edu>
[not found] ` <m37lw1w16u.fsf@vvv.vsu.ru>
1998-12-09 20:46 ` Shenghuo ZHU
1998-12-10 8:54 ` Vladimir Volovich
1998-12-10 18:27 ` Vladimir Volovich
1998-12-10 20:31 ` Michael Welsh Duggan
1998-12-10 20:57 ` Vladimir Volovich [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=m31zm7zpe6.fsf@vvv.vsu.ru \
--to=vvv@vvv.vsu.ru \
/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).