* current cvs version is badly BROKEN
@ 2000-05-03 14:55 Vladimir Volovich
0 siblings, 0 replies; 4+ messages in thread
From: Vladimir Volovich @ 2000-05-03 14:55 UTC (permalink / raw)
Hi!
with current cvs version any attempt to send a message with 8-bit
cyrillic text leads to sending it in internal mule encoding instead of
mime encoding (mime headers are okay).
previewing (plain and raw) does not show a problem. The following is a
line with cyrillic text:
▄©▄Ю▄ч▄я▄п ▄ъ▄у▄Ю▄п.
Best,
v.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: current cvs version is badly BROKEN
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
1 sibling, 0 replies; 4+ messages in thread
From: Shenghuo ZHU @ 2000-05-04 21:24 UTC (permalink / raw)
>>>>> "VV" == Vladimir Volovich <vvv@vvv.vsu.ru> writes:
VV> "ZSH" == Shenghuo ZHU writes:
ZSH> I can not reproduce the bug. Did you use unplugged mode to send
ZSH> the mail?
VV> no, i used exactly the same ~/.emacs file as i've sent to you in
VV> previous mail. my gessages are sent via smtp server (see
VV> custom-set-variables in that file).
ZSH> Anyway, you can trace message-encode-message-body to see what
ZSH> happens in the buffer " message temp". The body is supposed to
ZSH> be encoded as 8-bit text.
VV> i'll try tomorrow...
Fixed. Note that you need recompile message.el too.
--
Shenghuo
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: current cvs version is badly BROKEN
2000-05-04 20:30 ` current cvs version is badly BROKEN (test: ·ÔàÐÒáâÒãÙâÕ!) Vladimir Volovich
@ 2000-05-04 21:04 ` Shenghuo ZHU
2000-05-04 21:24 ` Shenghuo ZHU
1 sibling, 0 replies; 4+ messages in thread
From: Shenghuo ZHU @ 2000-05-04 21:04 UTC (permalink / raw)
>>>>> "VV" == Vladimir Volovich <vvv@vvv.vsu.ru> writes:
VV> "ZSH" == Shenghuo ZHU writes:
ZSH> I can not reproduce the bug. Did you use unplugged mode to send
ZSH> the mail?
VV> no, i used exactly the same ~/.emacs file as i've sent to you in
VV> previous mail. my gessages are sent via smtp server (see
VV> custom-set-variables in that file).
ZSH> Anyway, you can trace message-encode-message-body to see what
ZSH> happens in the buffer " message temp". The body is supposed to
ZSH> be encoded as 8-bit text.
VV> i'll try tomorrow...
Got it. It is because smtp-send-it uses a multibyte buffer to copy the
encoded 8-bit message from Gnus, which results double-decoded. Some
workarounds are needed.
--
Shenghuo
^ permalink raw reply [flat|nested] 4+ messages in thread
* current cvs version is badly BROKEN
@ 2000-05-03 14:52 Vladimir Volovich
2000-05-03 16:08 ` current cvs version is badly BROKEN (test: úÄÒÁ×ÓÔ×ÕÊÔÅ!) Shenghuo ZHU
0 siblings, 1 reply; 4+ messages in thread
From: Vladimir Volovich @ 2000-05-03 14:52 UTC (permalink / raw)
Hi!
with current cvs version any attempt to send a message with 8-bit
cyrillic text leads to sending it in internal mule encoding instead of
mime encoding (mime headers are okay).
previewing (plain and raw) does not show a problem. The following is a
line with cyrillic text:
▄©▄Ю▄ч▄я▄п ▄ъ▄у▄Ю▄п.
Best,
v.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2000-05-04 21:24 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-05-03 14:55 current cvs version is badly BROKEN Vladimir Volovich
-- strict thread matches above, loose matches on Subject: below --
2000-05-03 14:52 Vladimir Volovich
2000-05-03 16:08 ` current cvs version is badly BROKEN (test: úÄÒÁ×ÓÔ×ÕÊÔÅ!) Shenghuo ZHU
2000-05-04 7:34 ` current cvs version is badly BROKEN (test: Здравствуйте!) Vladimir Volovich
2000-05-04 14:59 ` 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
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).