From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: article editing oddity
Date: 12 Nov 1999 11:39:10 +0300 [thread overview]
Message-ID: <m3so2cp0i9.fsf@vvv.vsu.ru> (raw)
Hi,
i've got a message which was in windows-1251 encoding, but
Content-Type header said that it was in koi8-r, so the message was
unreadable.
I pressed C-u g e, and changed "charset=koi8-r" to
"charset=windows-1251" in the Content-Type header.
Then i pressed C-c C-c
But the saved article still contained "charset=koi8-r" !
What's going wrong? AFAIR, this worked with older gnus versions.
Best regards, -- Vladimir.
P.S. windows-1251 is defined in my .emacs file by
(codepage-setup 1251)
(define-coding-system-alias 'windows-1251 'cp1251)
next reply other threads:[~1999-11-12 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-12 8:39 Vladimir Volovich [this message]
1999-11-15 20:51 ` Lars Magne Ingebrigtsen
1999-11-15 21:23 ` Shenghuo ZHU
1999-12-01 14:37 ` Lars Magne Ingebrigtsen
1999-12-01 18:30 ` FAQ: show an article with a specified charset (was: Re: article editing oddity) Shenghuo ZHU
1999-12-01 23:00 ` Lars Magne Ingebrigtsen
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=m3so2cp0i9.fsf@vvv.vsu.ru \
--to=vvv@vvv.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).