From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: Re: strange CTE header
Date: 30 Dec 1998 18:56:19 +0100 [thread overview]
Message-ID: <861zlhqzss.fsf@slowfox.cs.uni-dortmund.de> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "30 Dec 1998 10:33:21 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
>
> > Outgoing messages with Latin 1 characters (äöü) are sent with CTE 8bit
> > rather than quoted-printable, even though
> > mm-content-transfer-encoding-defaults is
>
> rfc2047-default-charset and rfc2047-charset-encoding-alist also meddle
> here. I think some cleanup (or rather, simplification) in this area
> may be required, but I'm not sure...
Hm. Doing (setq rfc2047-default-charset 'us-ascii) produces an error
"Invalid coding system: us-ascii" when sending a message. (setq
rfc2047-default-charset nil) produces the same result as the default
value of iso-8859-1 -- CTE is 8bit.
Is my configuration broken?
kai
--
Just because I'm paranoid doesn't mean they're not out there to get me!
next prev parent reply other threads:[~1998-12-30 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-29 18:37 Kai.Grossjohann
1998-12-30 9:33 ` Lars Magne Ingebrigtsen
1998-12-30 17:56 ` Kai.Grossjohann [this message]
1999-01-02 13:10 ` 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=861zlhqzss.fsf@slowfox.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).