From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: bug in calculation of line length again
Date: 23 Nov 1998 14:37:10 -0500 [thread overview]
Message-ID: <5biug62obd.fsf@schnapps.cs.rochester.edu> (raw)
In-Reply-To: Vladimir Volovich's message of "23 Nov 1998 22:17:39 +0300"
>>>>> "VVV" == Vladimir Volovich <vvv@vvv.vsu.ru> writes:
VVV> "ZSH" == Shenghuo ZHU writes:
ZSH> I guess it is because of decoding. By reading codes of
ZSH> message-send-news, you can find that gnus does encoding before
ZSH> checking. Is it a proper order?
VVV> Perhaps, it is wrong. Some more detail: when the message does not
VVV> contain a `Newsgroups:' header (i.e. when it is a mail), gnus
VVV> behaves correctly (does not produce false warnings). When there
VVV> is a `Newsgroups:' header, gnus behaves wrong WRT line length
VVV> calculation (i just tested the very same message, with the only
VVV> difference: in the first case there was a Newsgroups header, and
VVV> in the second case there was To header).
message-send-mail does not check syntax.
ZSH> `(standard-display-8bit 160 255)' may relieve your pain.
VVV> But is it a Right Thing (TM) to use standard-display-8bit in a MULE
VVV> environment? I do not think so.
I do not really know whether it is or not. But it works for me. I
would rather see meaningless 8-bit strings than strings containing
lots of backslashes and numbers.
--
Shenghuo
next prev parent reply other threads:[~1998-11-23 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-23 8:02 Vladimir Volovich
1998-11-23 18:30 ` Shenghuo ZHU
1998-11-23 19:17 ` Vladimir Volovich
1998-11-23 19:37 ` Shenghuo ZHU [this message]
1998-11-24 10:00 ` Lars Magne Ingebrigtsen
1998-11-24 9:59 ` Lars Magne Ingebrigtsen
1998-11-24 13:49 ` Vladimir Volovich
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=5biug62obd.fsf@schnapps.cs.rochester.edu \
--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).