From: wmperry@aventail.com (William M. Perry)
Subject: Re: WIBNI
Date: 27 Aug 1999 14:05:12 -0500 [thread overview]
Message-ID: <86wvuhf3iv.fsf@megalith.bp.aventail.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "27 Aug 1999 20:19:48 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Lee Willis <lee@gbdirect.co.uk> writes:
>
> > ie I'd need to configure the four values
> >
> > MIME type Filter Args Output type
> > "application/msword" "mswordview" "-o -" "text/html"
> >
> > And he presto I get W3 rendering a copy of the word document as HTML in
> > the article buffer.
>
> William has described the chain for converting images, but I don't think
> a similar chain can exist for, er, documents. I mean, you can convert
> most any picture to most any other picture format, but you can't
> reasonably go from Frame to msword to postscript to html to LaTeX, or
> whatever.
Reason? We don't need no stinking reason! This is emacs after all, who
needs to be reasonable? :)
> So I think it would make more sense just to define a viewer for
> application/msword that converts to html and then hands it to w3.
Probably right, but...
Would be cool to have generic mime-type converting though. You could
extend the logic in images.el to arbitrary MIME types pretty easily though.
You might want to add a 'quality' parameter though, so that we don't just
blindly choose the shortest chain but at a lower total quality output.
Hmmm....
-Bill P.
next prev parent reply other threads:[~1999-08-27 19:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-14 9:52 WIBNI Lee Willis
1999-07-14 13:16 ` WIBNI Doug Bagley
1999-07-14 13:35 ` WIBNI wmperry
1999-08-27 18:19 ` WIBNI Lars Magne Ingebrigtsen
1999-08-27 19:05 ` William M. Perry [this message]
1999-08-27 19:19 ` WIBNI Lars Magne Ingebrigtsen
1999-08-27 19:56 ` WIBNI William M. Perry
1999-08-30 12:41 ` WIBNI Robert Bihlmeyer
1999-08-27 18:21 ` WIBNI Lars Magne Ingebrigtsen
1999-10-11 15:37 WIBNI Lee Willis
1999-11-06 21:51 ` WIBNI Lars Magne Ingebrigtsen
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=86wvuhf3iv.fsf@megalith.bp.aventail.com \
--to=wmperry@aventail.com \
/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).