From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Malformed charsets in content-type header.
Date: Wed, 29 May 2002 19:04:34 +0200 [thread overview]
Message-ID: <vafit56lwbh.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <vpqwutnt6m9.fsf@montrose.imag.fr> (Matthieu Moy's message of "Wed, 29 May 2002 15:40:14 +0200")
Matthieu Moy <Matthieu.Moy@imag.fr> writes:
> Would it be possible to recognize this broken behavior automatically ?
See the variable mm-charset-synonym-alist.
kai
--
Silence is foo!
next prev parent reply other threads:[~2002-05-29 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 13:40 Matthieu Moy
2002-05-29 17:04 ` Kai Großjohann [this message]
2002-05-29 17:18 ` Matthieu Moy
2002-05-29 19:30 ` Florian Weimer
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=vafit56lwbh.fsf@INBOX.auto.gnus.tok.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).