Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: MIME handling for common MS Windows attachments?
Date: 12 Jan 1999 20:13:04 +0100	[thread overview]
Message-ID: <kigzp7oe24f.fsf@jagor.srce.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "12 Jan 1999 18:25:28 +0100"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Defaulting *.doc to ms-word is bad,

Agreed.

> but I see no harm in defaulting application/ms-word to MS Word (or
> something else that can understand these files).

And agreed.

> Could someone who uses stuff like that mail me a patch for
> mailcap.el?

I've now asked around, it seems things are not as easy as I thought.
If we discount the giant stuff such as StarOffice (and, of course, The
Real Thing on Windows-running Emacsen), a useful default can be
constructed.  There is an `mswordview' that can grok *some* of the
Word formats (only Word 97, I'm told.)  We need to do the following:

1) Look at the contents of the part, and see if it is something
   mswordview can grok (one should study mswordview source to see how
   this is done).

2) If yes, then invoke mswordview which will produce HTML.  Feed the
   resulting HTML to W3.

3) If mswordview cannot grok it, it displays a list of other programs, 
   which supposedly can.  We should look into using them.

Not a bright future, all in all.

The following information provided by Drazen Kacar <dave@srce.hr>:

> A more sticky issue is whether to default image/* to the un-free,
> but commonly installed xv, or to some free image viewing program.
[...]
> (Well, it isn't really a sticky issue, because we could default to
> free programs, and then use non-free programs as the backup default
> values if the free programs don't exist on the system.)

The trouble is that xv is much better than most of the other stuff out 
there, especially for 8bit displays.  Defaulting to free stuff might
be a politically good idea, but it's a lousy choice for users.

> What image viewing programs exist out there?

There is imlib/gtk-based gqview, then there's ee (Electric Eyes) (also
imlib-based), ImageMagick's display (it produces high quality display,
but it's very slow, making it unsuitable for MIME viewers).


  parent reply	other threads:[~1999-01-12 19:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-12 14:46 John Cooper
     [not found] ` <m37lusset2.fsf@peorth.gweep.net>
1999-01-12 16:28   ` Hrvoje Niksic
1999-01-12 17:25     ` Lars Magne Ingebrigtsen
1999-01-12 19:07       ` Karl Eichwalder
1999-01-12 19:37         ` Hrvoje Niksic
1999-01-15 17:56           ` Karl Eichwalder
1999-01-12 19:13       ` Hrvoje Niksic [this message]
1999-01-13  7:51         ` Steinar Bang
1999-01-13  9:38         ` Russ Allbery
1999-01-13 14:13           ` Karl Kleinpaste
1999-01-13 15:50           ` Alan Shutko
1999-01-13 18:43           ` Lars Magne Ingebrigtsen
1999-01-14  0:58             ` Russ Allbery
1999-01-14 16:14               ` Hrvoje Niksic
1999-01-13 17:12       ` Matt Armstrong
1999-01-13 18:16         ` William M. Perry
1999-01-13 15:54     ` Robert Pluim
1999-01-13 16:27       ` William M. Perry
1999-01-13 22:35       ` Kai.Grossjohann
1999-01-14 11:53       ` John Cooper
1999-01-14 12:51         ` John Cooper
1999-01-14 15:14       ` Robert Bihlmeyer
1999-01-14 15:25         ` Robert Pluim
1999-01-14 19:20         ` Lars Magne Ingebrigtsen
1999-01-14 20:10           ` William M. Perry
1999-01-14 21:12             ` 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=kigzp7oe24f.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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).