Gnus development mailing list
 help / color / mirror / Atom feed
From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: 5.8.2 bug#1: test
Date: 17 Dec 1999 17:25:33 -0500	[thread overview]
Message-ID: <2naen9ryqq.fsf_-_@tiger.jia.vnet> (raw)
In-Reply-To: Vladimir Volovich's message of "18 Dec 1999 00:58:13 +0300"

>>>>> "VV" == Vladimir Volovich <vvv@vvv.vsu.ru> writes:

ZSH> Maybe I should test it using iso-8859-5 instead of koi8-r.

VV> hmm.. your message contains cyrillic encoded in iso-8859-5, not
VV> koi8-r.

I sent two messages. The other is encoded in koi8-r.

VV> i have two questions:

VV> 1) why the subject of this letter is partially brokenly encoded by
VV> gnus (i'm writing this letter from pgnus 0.99)? (cyrillic word
VV> followed by latin-1 word without a space were encoded brokenly,
VV> but cyrillic word followed by latin-1 word with a space between
VV> them was encoded correctly. does the current version of gnus
VV> behave as buggy as pgnus 0.99 in this situation?)

I think it is the problem of rfc2047-dissect-region. The MIME charset
depended on the first non-ascii MULE charset in words, therefore, the
order is sensitive. Now, I've rewritten the function, fixing the bug.

VV> 2) when displaying subjects in an *Article* buffer, gnus displays
VV> several lines, instead of just one (as in the summary
VV> buffer). this violates interpretation of linear spaces given in
VV> RFC-2047, doesn't it?

I only found the explicit description about CRLF between
encoded-words, nothing for other cases, i.e. what you saw. If you can
find the description. Please post it.

-- 
~{VlJ$;p~}



      reply	other threads:[~1999-12-17 22:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-15 16:10 5.8.2 bug#1: test тестtéßt test Vladimir Volovich
1999-12-15 16:20 ` 5.8.2 bug#2: " Vladimir Volovich
1999-12-17 10:01   ` 5.8.2 bug#2: test ~~~~téßt test Shenghuo ZHU
1999-12-15 16:48 ` 5.8.2 bug#1: test тестtéßt test Vladimir Volovich
1999-12-17 15:43   ` 5.8.2 bug#1: test тестtéßt test тест téßt Shenghuo ZHU
1999-12-17 17:07     ` 5.8.2 bug#1: test ^[,LbUab^[(Btéßt test тестtéßt Vladimir Volovich
1999-12-17 18:24       ` 5.8.2 bug#1: test тестtéßt test тест téßt Shenghuo ZHU
1999-12-17 18:26         ` Shenghuo ZHU
1999-12-17 19:28           ` 5.8.2 bug#1 blah blah blah Florian Weimer
1999-12-18 13:32             ` Hrvoje Niksic
1999-12-17 21:58           ` 5.8.2 bug#1: test ^[,LbUab^[(Btéßt test тестtéßt Vladimir Volovich
1999-12-17 22:25             ` 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=2naen9ryqq.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).