From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: rfc2047-decode-string
Date: 09 Nov 2000 23:50:19 +0300 [thread overview]
Message-ID: <m366lwrhtg.fsf@vvv.vsu.ru> (raw)
Hi,
i received a message in which gnus did not decode the subject.
it looked like:
Subject: =?koi8-r?B?UmU6IG1zIG9mZmljZSAyMDAwLCDe1M/CIMXHzy4uLg?=
i think that perhaps the string is not encoded 100% correctly, -- it
lacks two figns `==' at the end:
(rfc2047-decode-string "=?koi8-r?B?UmU6IG1zIG9mZmljZSAyMDAwLCDe1M/CIMXHzy4uLg?=")
"=?koi8-r?B?UmU6IG1zIG9mZmljZSAyMDAwLCDe1M/CIMXHzy4uLg?="
(rfc2047-decode-string "=?koi8-r?B?UmU6IG1zIG9mZmljZSAyMDAwLCDe1M/CIMXHzy4uLg==?=")
"Re: ms office 2000, чтоб его..."
would it be possible, nevertheless, to make rfc2047-decode-string more
liberal to this sort of `bugs' in encoded-words?
Best regards, -- Vladimir.
next reply other threads:[~2000-11-09 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 20:50 Vladimir Volovich [this message]
2000-11-09 21:25 ` rfc2047-decode-string 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=m366lwrhtg.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).