From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Character set thingies
Date: 30 Aug 1998 17:57:55 +0200 [thread overview]
Message-ID: <m3u32ulaws.fsf@sparky.gnus.org> (raw)
Ok; then (barring all the gazillion bugs I'm sure there's in the code)
Gnus should now be RFC1522 compliant. (That is, all the headers
should be properly encoded.)
Now, how does one turn that off? :-)
When I send out mail messages (and news articles) containing only
Latin-1 characters, I do not want Gnus to encode those. What would be
the most convenient way to specify charsets not to encode? Hm...
Perhaps just an `rfc1522-unencoded-charsets' variable that would
default to `(ascii)' or `(ascii iso-8859-1)'? Yes, I think I'll do
that.
But what if one wants to encode mail, but not news? Or the other way
around? Hm.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next reply other threads:[~1998-08-30 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-30 15:57 Lars Magne Ingebrigtsen [this message]
1998-08-30 16:09 ` Hrvoje Niksic
1998-08-30 16:36 ` Lars Magne Ingebrigtsen
1998-08-30 17:05 ` Hrvoje Niksic
1998-08-30 17:38 ` 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=m3u32ulaws.fsf@sparky.gnus.org \
--to=larsi@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).