Re: Different content types with nnweb?

[Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)]

On 27 May 2001, David Z. Maze wrote:

> I'm mildly abusing nnweb into acting as a front-end to the Debian
> bug-tracking system.  This is actually going pretty well so far,
> since I can toss together a list of "articles" out of a package's
> bug-list page, and nnweb will present that in the summary buffer.
> So far, so good.

Way cool.

> What I'd like to do for a first pass is to read in the page
> containing all of the traffic for a particular bug, slap some
> headers on to it, and just have Gnus display it as an HTML page.  If
> I put "Content-Type: text/html" at the front of the article, though,
> Gnus seems to just ignore it; the body is just displayed as
> (unformatted) HTML.  Is there some trick to making this work?

Make sure it's in the header, not the body.  Also you will need
`Mime-Version: 1.0', I think.  Hm.  And if it isn't ascii, you need a
charset declaration, too.  But maybe you can extract that from the
HTML generated by the Debian thingy.

To summarize:

Content-type: text/html; charset=utf-8
Mime-Version: 1.0
Content-transfer-encoding: 8bit

> (And what I'd *really* like to do is translate the page into
> something along the lines of a normal digest.  Are there any
> pointers as to the format I should use for this?  [Didn't gnus.org
> used to have links to useful RFCs somewhere?]  Can I co-opt mml,
> create an mml document from the HTML page, and then translate that
> into something viewable as an article?)

Hm.  There are different formats.  But surely, maybe MIME would be
best.  I guess you can use mml-generate-mime for MML->MIME conversion.

kai
-- 
~/.signature: No such file or directory