From: Steinar Bang <sb@metis.no>
Subject: Re: Charset cleanup
Date: 18 Jan 1999 10:07:13 +0100 [thread overview]
Message-ID: <whzp7hq79a.fsf@viffer.oslo.metis.no> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "15 Jan 1999 21:47:08 +0100"
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
> 4) There will be a gnus-group-post-charset-alist variable, which says what
> the default charset in groups that match the keys will be. The
> default will include things like
> ("^no\\." iso-8859-1)
> which means that characters from this charset wont be RFC2047-encoded
> when posting to Norwegian groups, for instance.
Umm... I saw that a pgnus 0.71 user (Bjørn Mork) had taken som flak
for posting with RFC2047 headers on no.alt.motorsykler, during the
weekend.
So this probably didn't work out quite right at first...
next prev parent reply other threads:[~1999-01-18 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-15 20:47 Lars Magne Ingebrigtsen
1999-01-18 9:07 ` Steinar Bang [this message]
1999-01-18 14:33 ` 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=whzp7hq79a.fsf@viffer.oslo.metis.no \
--to=sb@metis.no \
/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).