TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Acrobat From:"Marvin W. Miller" <Marvin_Miller -at- SEC -dot- SEL -dot- SONY -dot- COM> Date:Mon, 5 Feb 1996 08:40:55 -0800
My experience with Acrobat has been that the files sizes are smaller than than
the original document. We use Acrobat for internal distribution of project
docs over the company network (via web pages).
> Earlier correspondents write:
> >>You can use Acrobat to distribute a document on the web while
> >>retaining its exact paper look.
> >Cool! But why would I want to do this?
> Acrobat solves a different problem from the one HTML addresses.
> Much of traditional publishing suffers from the costs and delays
> inherent in the following cycle:
> 1. Determine the content and decide how it should look on the page.
> 2. Render it on dead trees.
> 3. Deliver it to its destination.
> Huge benefits accrue to the publisher from swapping steps 2 and 3.
> It reduces publication delay and shifts printing costs to the
> consumer. Acrobat makes this possible. ...RM
> My very limited experience with Acrobat has been its large file size.
> OK, there's plenty of space on a CD-ROM, but we're being encouraged
> to send Acrobat files over the Internet, or am I wrong?