Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@metis.no>
Subject: Re: Web-based mailreading enhancement
Date: 11 Oct 1996 15:10:02 +0200	[thread overview]
Message-ID: <whwwwxejf9.fsf@norne.metis.no> (raw)
In-Reply-To: Steinar Bang's message of 11 Oct 1996 11:15:41 +0200

>>>>> Steinar Bang <sb@metis.no>:

> [snip! on reading web mailing list archives with Gnus]
>>>>> Wesley.Hardaker@sphys.unil.ch:

>> Unfortunately, most mailing lists differ in the web backend they
>> use.  (or does listserv come with a standard?)  The last time I
>> looked for mail-to-web type software the list was something like
>> 10-20 packages long...

> Well, if we could support the 1 or 2 most used (starting with
> hypermail), I think that would get us pretty far.  Most of the
> archives I've seen, have been hypermail archives.

> There *may* be a problem with missing information in the generated
> HTML code, however...

I looked at some stuff generated by hypermail.  Much of this auxillary
information can be found in SGML/HTML comments at the start.  Head
(slightly edited to protect the innocent) of a typical hypermail file:

<!-- received="Fri Oct 11 14:42:52 1996 MET DST" -->
<!-- sent="Fri, 11 Oct 1996 14:42:36 +0200" -->
<!-- name="Steinar Bang" -->
<!-- email="sb@metis.no" -->
<!-- subject="Something testing" -->
<!-- id="199610111242.NAA20690@client.metis.no" -->
<!-- inreplyto="" -->
<title>Somestupidarchivenamehere: Something testing</title>
<h1>Something testing</h1>
Steinar Bang (<i>sb@metis.no</i>)<br>
<i>Fri, 11 Oct 1996 14:42:36 +0200</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#290">[ date ]</a><a href="index.html#290">[ thread ]</a><a href="subject.html#290">[ subject ]</a><a href="author.html#290">[ author ]</a>
<!-- next="start" -->
<li> <b>Previous message:</b> <a href="0289.html">Hogne Tjemsland: "Re: C++ file extensions"</a>
<!-- nextthread="start" -->
</ul>
<!-- body="start" -->

The rest is HTML'ized code of the original message text body.  Message
paragraphs are turned into HTML paragraphs.  Each line ends with a
<br> element to preserve line length.



  reply	other threads:[~1996-10-11 13:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-10-10  9:22 Jan Vroonhof
1996-10-10 22:39 ` Lars Magne Ingebrigtsen
1996-10-11  6:45   ` Wesley.Hardaker
1996-10-11  9:15     ` Steinar Bang
1996-10-11 13:10       ` Steinar Bang [this message]
1996-10-11 13:15         ` Lars Magne Ingebrigtsen
1996-10-11 14:33           ` Steinar Bang
1996-10-12 18:42             ` Lars Magne Ingebrigtsen
1996-10-12 18:44               ` Steinar Bang
1996-10-13  1:02               ` Raja R Harinath
1996-10-13 17:19               ` William Perry
1996-10-13 17:31               ` Steven L Baur
1996-10-14 20:10                 ` Lars Magne Ingebrigtsen
1996-10-11 15:58           ` William Perry
1996-10-12 18:45             ` Lars Magne Ingebrigtsen
1996-10-12  0:00           ` Joe Wells
1996-10-11 10:54     ` Lars Magne Ingebrigtsen
1996-10-14 14:59   ` Using groups as spool Jan Vroonhof
1996-10-14 15:28     ` Kai Grossjohann

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=whwwwxejf9.fsf@norne.metis.no \
    --to=sb@metis.no \
    /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).