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: HTML vs. Adobe Acrobat From:Benjamin Milstead <guilden -at- IQUEST -dot- NET> Date:Thu, 21 Mar 1996 21:41:22 -0500
I think you've made a reasonable decision, especially if you want to =
preserve design integrity. However, you've lost some extensibility and =
audience by not converting to HTML. To what extent you've lost it =
depends upon the content and purpose of your documents, but the fact =
remains that far more Web users use Netscape than they do Acrobat =
Reader. =20
Cheers,
Ben Milstead
My company recently decided to stop investigating tools for
converting our FrameMaker products to HTML for distribution
on the web. Instead, they have decided to use the Adobe
Acrobat suite of products to provide our documents on-line
and on CD-ROM, with a search capability.
Can anyone tell me what functionality we would get from
converting our FrameMaker documents to HTML that we will
not get from the Adobe suite of products? In other words,
did we make the right decision?
