From: Andreas Schwab <schwab@suse.de>
Subject: Re: quoted-printable sucks
Date: 21 Jul 1999 12:30:39 +0200 [thread overview]
Message-ID: <je673e9tww.fsf@hawking.suse.de> (raw)
In-Reply-To: Karl Kleinpaste's message of "Tue, 20 Jul 1999 17:40:51 GMT"
Karl Kleinpaste <karl@justresearch.com> writes:
|> It seems to me that I used to be able to compose mail messages which
|> were routinely sent as 8bit, iso-8859-1, and I didn't have to do
|> anything special to make that happen. Now (p0.95), it seems that
|> messages with "interesting" characters in them are still sent as
|> iso-8859-1, but Gnus wants to q-p'ify my universe rather than sending
|> them 8bit.
|>
|> Is there some tweak in the vicinity of p0.9x that I was supposed to
|> make, to keep things happening 8bit-ish?
I'm doing this:
(eval-after-load "mm-bodies"
'(setcdr (assq 'iso-8859-1 mm-body-charset-encoding-alist)
'8bit))
Dunno if there is anything more straight forward.
--
Andreas Schwab "And now for something
schwab@suse.de completely different."
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
next prev parent reply other threads:[~1999-07-21 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-20 17:39 Karl Kleinpaste
1999-07-21 10:30 ` Andreas Schwab [this message]
1999-07-21 12:09 ` Max Froumentin
1999-08-27 20:43 ` 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=je673e9tww.fsf@hawking.suse.de \
--to=schwab@suse.de \
/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).