From: "François Pinard" <pinard@iro.umontreal.ca>
Subject: Re: Pterodactyl Gnus v0.46 is released
Date: 18 Nov 1998 16:57:55 -0500 [thread overview]
Message-ID: <oq90h8u0ik.fsf@icule.progiciels-bpi.ca> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "18 Nov 1998 07:36:24 +0100"
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Is it common to send multipart messages that only contain a single part?
Not really common, yet I remember having (softly :-) complained to a few
of my correspondents who were always doing that.
> Why would people do that?
Presumably because they do not have full control over their MUAs?
> > And how 'bout decoding the ugly `=?ISO...?=' encodings that appear in
> > headers of some messages, particularly ones posted with TM/SEMI?
> I haven't seen any Q encodings of headers in eons. Could you give us
> an example?
Do you mean RFC1522 (now RFC2070, if not mistaken)?
Even if ugly, these address a real need. Of course, you'll more likely
see B for messages showing Asian names, but for Latin languages sharing
many letters with the English alphabet, Q is still likely to occur.
--
François Pinard mailto:pinard@iro.umontreal.ca
Join the free Translation Project! http://www.iro.umontreal.ca/~pinard
next prev parent reply other threads:[~1998-11-18 21:57 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-15 1:01 Lars Magne Ingebrigtsen
1998-11-15 21:49 ` Graham Murray
1998-11-16 8:18 ` Graham Murray
1998-11-17 23:38 ` Lars Magne Ingebrigtsen
1998-11-18 3:17 ` Alexandre Oliva
1998-11-18 6:36 ` Lars Magne Ingebrigtsen
1998-11-18 6:53 ` Alexandre Oliva
1998-11-18 7:27 ` Lars Magne Ingebrigtsen
1998-11-18 7:36 ` Alexandre Oliva
1998-11-18 8:12 ` Lars Magne Ingebrigtsen
1998-11-18 8:22 ` Kai.Grossjohann
1998-11-18 8:42 ` Lars Magne Ingebrigtsen
1998-11-18 21:57 ` François Pinard [this message]
1998-11-19 5:57 ` Lars Magne Ingebrigtsen
1998-11-19 11:31 ` Hrvoje Niksic
1998-11-19 11:46 ` Lee Willis
1998-11-19 11:50 ` Hrvoje Niksic
1998-11-20 1:51 ` Lars Magne Ingebrigtsen
1998-11-19 16:23 ` François Pinard
1998-11-19 21:01 ` Edward J. Sabol
1998-11-19 22:29 ` François Pinard
1998-11-20 1:57 ` Lars Magne Ingebrigtsen
1998-11-20 10:25 ` No more buttons by default? Hrvoje Niksic
1998-11-20 13:15 ` Steinar Bang
1998-11-20 15:37 ` Lars Magne Ingebrigtsen
1998-11-20 17:30 ` Karl Kleinpaste
1998-11-20 17:45 ` Steinar Bang
1998-11-20 17:48 ` Steinar Bang
1998-11-21 4:29 ` Lars Magne Ingebrigtsen
1998-11-21 8:12 ` Dale Hagglund
1998-11-21 8:49 ` Lars Magne Ingebrigtsen
1998-11-21 9:19 ` Dale Hagglund
1998-11-21 18:14 ` Matt Armstrong
1998-11-20 15:13 ` François Pinard
1998-11-22 12:06 ` Hrvoje Niksic
1998-11-24 9:29 ` Lars Magne Ingebrigtsen
1998-11-20 15:28 ` Lars Magne Ingebrigtsen
1998-11-20 17:56 ` Raja R Harinath
1998-11-20 18:07 ` Kai.Grossjohann
1998-11-21 4:31 ` Lars Magne Ingebrigtsen
1998-11-20 12:19 ` Pterodactyl Gnus v0.46 is released Kai.Grossjohann
1998-11-20 12:35 ` Kai.Grossjohann
1998-11-20 15:26 ` François Pinard
1998-11-20 12:12 ` Kai.Grossjohann
1998-11-20 15:17 ` François Pinard
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=oq90h8u0ik.fsf@icule.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
/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).