From: Samuel Tardieu <sam@ada.eu.org>
Cc: ding@gnus.org
Subject: Re: [fr.comp.lang.ada] Re: GNAT 3.12p pour Linux et Sparc Solaris
Date: 03 Nov 1999 16:10:32 +0100 [thread overview]
Message-ID: <1999-11-03-16-10-32+trackit+sam@ada.eu.org> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "03 Nov 1999 11:21:33 +0100"
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 382 bytes --]
>>>>> "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
Kai> See the variable gnus-group-charset-alist.
I'm not complaining about the charset, I'm complaining about the
quoted printable thing. No news message should use this, at least as
long as the standard news charset (latin1) or any subset (us-ascii) is
used.
Sam
--
Samuel Tardieu -- sam@ada.eu.org
next prev parent reply other threads:[~1999-11-03 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-03 8:30 Samuel Tardieu
1999-11-03 10:21 ` Kai Großjohann
1999-11-03 15:10 ` Samuel Tardieu [this message]
1999-11-03 15:15 ` Kai Großjohann
1999-11-03 15:18 ` Toby Speight
1999-11-03 18:07 ` Samuel Tardieu
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=1999-11-03-16-10-32+trackit+sam@ada.eu.org \
--to=sam@ada.eu.org \
--cc=ding@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).