From: lark@world.std.com (Lar Kaufman)
To: blinux-list@redhat.com, blinux-list@redhat.com
Subject: Re: File conversion question
Date: Thu, 9 Jul 1998 09:03:12 -0400 [thread overview]
Message-ID: <199807091303.AA21133@world.std.com> (raw)
In-Reply-To: <Pine.SUN.3.95.980709143838.4902A-100000@ariel.ucs.unimelb.EDU.AU>
Aladdin ghostscript converts pdf and postscript to a multitude of output
forms, including plain or formatted text. It's powerful and complex, however.
It is a lot easier to use pstoedit as a front-end (and pstoedit can also
manage other modules for additional conversions). There is one nasty PDF
trick that is sometimes used online--a decryption key is added to the PDF
file. Ghostscript can also process those PDF files, but you have to download
the decryption module from a non-U.S. website, because it's export-restricted
technology. (Still!)
Get ghostscript from <http://www.aladdin.com>. The GNU ghostscript package
can't process PDF (or even PostScript level 2) so you need Aladdin's version
4.01 or later. It's been a long time since I checked, but pstoedit should
be in usual Linux websites. I'll have to research where to get the
decryption module, if you should need it.
I'm interested whether anyone is using these tools "on the fly" for
netsurfing. If so, could you share info on how to set it up? I have
always captured the files and converted them later, but I'm interested
in integrating and automating the conversions, preferably from within
emacs.
-lar
Lar Kaufman | "It's bad enough to see yourself as the world is seeing
Polymedia Services | you now. To see yourself as the world saw you in the
Concord, Mass. | immediate past is to see yourself tantalizingly beyond
lark@walden.com | any hope of redemption." - Roy Blount Jr.
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Jason White
` wlestes
` Lar Kaufman [this message]
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=199807091303.AA21133@world.std.com \
--to=lark@world.std.com \
--cc=blinux-list@redhat.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).