From: vvv@vsu.ru
Subject: bug in encoded-word encoding
Date: 18 Feb 2001 14:46:46 +0300 [thread overview]
Message-ID: <eyae7kkyc9.fsf@video.uic.vsu.ru> (raw)
Hi,
i wrote:
> sorry for wrong quote from RFC. i wonder, is this still a buggy
> behavior?
looks like yes:
RFC2047> Ordinary ASCII text and 'encoded-word's may appear together in the
RFC2047> same header field. However, an 'encoded-word' that appears in a
RFC2047> header field defined as '*text' MUST be separated from any adjacent
RFC2047> 'encoded-word' or 'text' by 'linear-white-space'.
Best,
v.
next reply other threads:[~2001-02-18 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 11:46 vvv [this message]
2001-02-18 13:55 ` ShengHuo ZHU
2001-02-20 16:07 ` vvv
-- strict thread matches above, loose matches on Subject: below --
2001-02-18 11:43 vvv
2001-02-18 11:39 vvv
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=eyae7kkyc9.fsf@video.uic.vsu.ru \
--to=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).