From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Control CTE with Gcc
Date: Tue, 08 Feb 2000 15:20:37 +0100 [thread overview]
Message-ID: <vaf900v6aiy.fsf@lucy.cs.uni-dortmund.de> (raw)
Some people write copies of their mail with Gcc. For people using
iso-8859, mails with non-ascii characters may be encoded qp or base64,
depending on their content. This is suboptimal for searching in the
mails; for this application one needs a consistent encoding of all text
parts, and 8bit encoding is probably best.
WIBNI it was possible to tell Gnus to write all text/* parts using a
specific encoding with Gcc?
kai
--
~/.signature: No such file or directory
next reply other threads:[~2000-02-08 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-08 14:20 Kai Großjohann [this message]
2000-04-20 22:57 ` Lars Magne Ingebrigtsen
2000-04-21 9:55 ` Kai Großjohann
2000-04-21 11: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=vaf900v6aiy.fsf@lucy.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).