From: Vladimir Volovich <vvv@vvv.vsu.ru>
Cc: test@test.vsu.ru
Subject: Re: current cvs version is badly BROKEN (test: Здравствуйте!)
Date: 04 May 2000 11:34:50 +0400 [thread overview]
Message-ID: <eyn1m6dazp.fsf@video.uic.vsu.ru> (raw)
In-Reply-To: Shenghuo ZHU's message of "03 May 2000 12:08:48 -0400"
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> VV> with current cvs version any attempt to send a message with 8-bit
> VV> cyrillic text leads to sending it in internal mule encoding
> VV> instead of mime encoding (mime headers are okay).
>
> Where did you put the 8-bit cyrillic text? In the body or the subject?
> What is your setting to send it in 8-bit?
I've put it into the body. I did not test whether 8-bit text is broken
in the subject with current cvs version (as it is in the body).
I've gotten the current cvs version and run gnus with the following
~/.emacs file (no ~/.gnus), and the behavior seems to be still broken:
cyrillic text in the body of this message (in the quote below) is sent
not in koi8-r but in internal mule encoding.
[-- Attachment #2: Type: application/emacs-lisp, Size: 1328 bytes --]
[-- Attachment #3: Type: text/plain, Size: 157 bytes --]
> Test text: ▄╥▄т▄Ю▄п▄р▄А▄Б▄р▄Ц▄ы▄Б▄у!
>
> The test Cyrillic text of this message should be encoded in 8-bit. So
> does the text in the subject.
Best,
v.
next prev parent reply other threads:[~2000-05-04 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-03 14:52 current cvs version is badly BROKEN Vladimir Volovich
2000-05-03 16:08 ` current cvs version is badly BROKEN (test: úÄÒÁ×ÓÔ×ÕÊÔÅ!) Shenghuo ZHU
2000-05-04 7:34 ` Vladimir Volovich [this message]
2000-05-04 14:59 ` current cvs version is badly BROKEN (test: Здравствуйте!) Shenghuo ZHU
2000-05-04 20:30 ` current cvs version is badly BROKEN (test: ·ÔàÐÒáâÒãÙâÕ!) Vladimir Volovich
2000-05-04 21:04 ` current cvs version is badly BROKEN Shenghuo ZHU
2000-05-04 21:24 ` 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=eyn1m6dazp.fsf@video.uic.vsu.ru \
--to=vvv@vvv.vsu.ru \
--cc=test@test.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).