From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: word-encoder creates short lines; possible bug in encoder
Date: 01 Jun 2000 10:33:20 -0400 [thread overview]
Message-ID: <2nln0psc7j.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Vladimir Volovich's message of "01 Jun 2000 13:54:41 +0400"
>>>>> "VV" == Vladimir Volovich <vvv@vvv.vsu.ru> writes:
VV> Hi!
VV> 1. when gnus uses encoded-word encoding (of type B or Q) in headers,
VV> it tends to create more short lines than necessary. Say, i received a
VV> message with subject:
VV> Subject: =?koi8-r?B?Iu7P18HRINDB0sHEycfNwSDEzNEg09TB0s/KINTFz9LJySI=?=
VV> when replying to this message, gnus created a subject like:
VV> Subject: Re: "=?koi8-r?b?7s/XwdEg0MHSwcTJx83B?=
VV> =?koi8-r?b?IMTM0SDT1MHSz8og1MXP?=
VV> =?koi8-r?b?0snJ?="
VV> it seems that gnus used AT LEAST one extra line, creating short lines
VV> in headers. Is it possible to change the function which encodes
VV> headers to use optimal line number (i.e. try to use the smallest
VV> possible number of lines, breaking only really wide lines)?
According to RFC2047,
Each 'encoded-word' MUST represent an integral number of
characters. A multi-octet character may not be split across
adjacent 'encoded-word's.
It is difficult to decide where to break the line. For the safety
reason, the subject is broken into several lines. If you can figure
out the optimal algorithm to break wide lines, that's great.
VV> 2. AFAIR, RFC says that encoded-word should not appear inside
VV> quotes. is the above header (created by gnus) correct in this
VV> respect? i mean "=?koi8-r?b? .... ?=" should the quotes be
VV> "hidden" inside encoded-word?
It is a bug.
Shenghuo
prev parent reply other threads:[~2000-06-01 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-01 9:54 Vladimir Volovich
2000-06-01 14:33 ` Shenghuo ZHU [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=2nln0psc7j.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).