EGCS web pages

[Gerald Pfeifer]

On 29 Oct 1998, Alexandre Oliva wrote:
>>> The mailing list archives currently include the literal text of
>>> messages mailed in.  That means, in particular, that messages
>>> containing '<' and '>' characters do not display right [...]
> OTOH, they allow you to save the web-page of an archived message
> containing source code or a patch, then extract the source code or
> patch from the saved file.  If `<' and other html meta-characters were
> mangled, you'd have to manually replace them in order to get the
> important data.

What's wrong with `lynx -dump URL`?

'<' and '>' are not a real issue with respect to that, though white
space may case troubles, I'm afraid.


And later Mark Mitchell <mark@markmitchell.com> wrote:
> That's what I meant. I said `cut-and-paste' as a shorthand, but
> `save-as-source' is what I really do.

With the new approach you could use `cut-and-paste' :-), for then the
web page would _display_ (instead of _contain_) the patch.


BTW, if presenting both HTML and regular text versions is not
easily feasible with a single tool, one could set up a newsserver
or web query interface where you can access mails based on Message-ID.

I.e., one could retrieve the Message-ID via the regular pages and then
obtain the original message by means of that additional service.

Gerald
-- 
Gerald Pfeifer (Jerry)      Vienna University of Technology
pfeifer@dbai.tuwien.ac.at   http://www.dbai.tuwien.ac.at/~pfeifer/