Gnus development mailing list
 help / color / mirror / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: ding@gnus.org
Subject: application/msword [was: Re: gnus-uu-post-insert-binary-in-article is not correct]
Date: 30 Jul 1998 18:46:33 -0400	[thread overview]
Message-ID: <vr67gf3qk6.fsf_-_@lagrande.iro.umontreal.ca> (raw)
In-Reply-To: Jochen_Hayek@acm.org's message of "Thu, 30 Jul 1998 21:48:49 GMT"

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]

Jochen_Hayek@acm.org writes:

>     >> !     ("\\.doc$" "application/msword")
> 
>     LMI> This one I can't accept.
>
> People know, you don't like MIME. (Sorry, I couldn't resist ...)

I do not know, and am merely joking here, but maybe the two letters "ms"
above are really the combination which Lars do not like :-).

> On the other hand: have you ever received a `.doc' file, that was not
> an MS Word file?

By the way, it is a part of my life that I often, too often receive `msword'
or `wordperfect' attachments in email.  For example, people working in some
ISO groups do that, and my frequent protests are apparently not heavy enough
to significantly change their habit.  At one place where I often work, I'm
almost alone to maintain a little cluster of Unix machines, little island
of peace, lost into a wide sea of hundreds and hundreds of NT's and 95's.
Secretaries and agents routinely and frequently send messages containing
Word files, Outlook notices, Excel (sp?) data, and such other things.
Besides me, everybody there seems to be happy.  Surely, I would never
succeed into converting them all, and I think it's me who should adapt...

So, for those few reasons, I'm now ready and willing to face the sad reality!
Is there any filter or tool, which *I* could run on Unix/Linux, available
in source form (of course), allowing me to somewhat handle such documents,
when they happen to come and pollute my Gnus mailgroups?  Are such files'
intimate format (Word, Wordperfect, and others) documented somewhere?

If I was able to find enough information, I might plan some new "surfaces"
in `recode' (who knows, some of you might know this tool? :-) for handling
these formats, and devise something to ease my Gnus ways in this...  Sigh!

-- 
François Pinard                            mailto:pinard@iro.umontreal.ca
Join the free Translation Project!    http://www.iro.umontreal.ca/~pinard


  reply	other threads:[~1998-07-30 22:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-27 14:25 gnus-uu-post-insert-binary-in-article is not correct Jochen_Hayek
1998-07-30 20:46 ` Lars Magne Ingebrigtsen
1998-07-30 21:48   ` Jochen_Hayek
1998-07-30 22:46     ` François Pinard [this message]
1998-07-31  4:28       ` application/msword [was: Re: gnus-uu-post-insert-binary-in-article is not correct] Andrew J Cosgriff
1998-07-31 10:29       ` Kai Grossjohann
1998-07-31 14:38         ` Jason R Mastaler
1998-07-31  8:18     ` gnus-uu-post-insert-binary-in-article is not correct Darren/Torin/Who Ever...
1998-08-03 14:22       ` Steinar Bang
1998-08-06 12:27         ` Jochen_Hayek
1998-08-06 13:48           ` Steinar Bang

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=vr67gf3qk6.fsf_-_@lagrande.iro.umontreal.ca \
    --to=pinard@iro.umontreal.ca \
    --cc=ding@gnus.org \
    /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).