From: "roodwriter@core.com" <roodwriter@core.com>
Subject: Re: How to convert .doc to txt
Date: Thu, 30 Oct 2003 13:28:31 -0500 [thread overview]
Message-ID: <vq2lvnhc060raf@corp.supernews.com> (raw)
In-Reply-To: y44llr2r4c0.fsf@nestle.ai.mit.edu
Don Saklad wrote:
> In rmail in emacs, how do you convert .doc to txt ?...
>
> It converted to pdf
> using the free thing at
> http://preprints.cern.ch/Convert?emailGuide
> but that new pdf wouldn't convert to ascii plain text.
>
>
> Nor did that new pdf convert to ascii plain text using the free thing at
> http://www.adobe.com/products/acrobat/access_onlinetools.html
I should start this out with the caveat that for some reason I can't receive
e-mail on Emacs. But for what it's worth.
Emacs doesn't have a built-in function to do this, sadly. For converting
.docs to text I use antiword. (I have a Linux box.) I save the .doc from my
regular e-mail program, go into Dired, and use the ! command to use
antiword. This translates the .doc into text in its own window. I then copy
it and paste it into another buffer.
I don't do this by hand anymore. I made a macro to do all this and bound a
shortcut key sequence to it.
Linux has several other ways to convert .docs to other things. Word2x
(uncapitalized) converts Word 6 files to LaTeX or text. wvWare (that's how
it's capitalized) converts to HTML.
There are more.
Be aware that none are perfect and there are some variations in the text
output. These are the ones I thought worked best. Best thing to do is
experiment.
I do what I can do avoid Word files. Whenever someone sends me one I
politely point out that not everyone has Word on their machine or will go
out and buy it just to read a few lines of text. I also note that plain
text, which is just a simple cutting and pasting job, can be read by
everyone at no risk. Many people avoid attachments because that's where the
viruses live.
It can also be easier for the sender because with plain text they're not
tempted to prettify what they're writing. If you need pretty there are PDFs
and HTMLs.
I've found that if you're nice and reasonable about it, most people will
comply. They had just never thought about it. I've even had a few thank me.
Only one has refused outright not to do it. Says she doesn't have the time.
I can't make her understand it probably takes less time since she won't be
wasting it on formatting.
So about twice a month I get a .doc file from her. The others I get are from
people sending me something for the first time or from people that just
forget.
The Free Software Foundation has a suggested text you can send back, but I
think it's too strong. Worth reading for ideas, though.
Hope this helps.
--Rod
--
Author of "Linux for Non-Geeks--Clear-eyed Answered for Practical Consumers"
and "Boring Stories from Uncle Rod." Both are available at
http://www.rodwriterpublishing.com/index.html
To reply by e-mail, take the extra "o" out of the name.
next prev parent reply other threads:[~2003-10-30 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 18:02 How to convert .doc to txt Don Saklad
2003-10-30 18:28 ` roodwriter [this message]
2003-11-11 14:14 ` Alex Ott
2003-11-11 15:10 ` Bruce Ingalls
2003-11-11 17:27 ` Thien-Thi Nguyen
2003-11-11 19:27 ` Dan Anderson
2003-11-11 17:00 ` Burton Samograd
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vq2lvnhc060raf@corp.supernews.com \
--to=roodwriter@core.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 read-only IMAP folder(s) and NNTP newsgroup(s).