From: Roman Belenov <roman@nstl.nnov.ru>
Cc: ding@gnus.org
Subject: Re: 8-bit again
Date: Thu, 03 Aug 2000 12:31:47 +0400 [thread overview]
Message-ID: <uzomuoido.fsf@nstl.nnov.ru> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Thu, 3 Aug 2000 09:49:56 +0200"
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> It appears that the function does some munging of the article, and
> maybe that munging does not assume that the message is mail? What
> happens if you tell gnus-group-posting-charset-alist to use 8bit for
> all groups that you use in the Gcc header -- does that produce 8bit
> Gcc'd copies?
No, I tried it but failed. Changing mm-body-charset-encoding-alist
helped.
--
With regards, Roman.
prev parent reply other threads:[~2000-08-03 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-02 18:43 Roman Belenov
2000-08-03 7:49 ` Kai Großjohann
2000-08-03 8:31 ` Roman Belenov [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=uzomuoido.fsf@nstl.nnov.ru \
--to=roman@nstl.nnov.ru \
--cc=ding@gnus.org \
/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).