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.
Re: Adobe PDF as Web solution (was: PageMaker to HTML)
Subject:Re: Adobe PDF as Web solution (was: PageMaker to HTML) From:Shmuel Ben-Artzi <sba -at- NETMEDIA -dot- NET -dot- IL> Date:Thu, 1 Aug 1996 18:08:17 +0200
Joe,
>I would love to use PDF as a delivery method for the web, but only about
>20 percent of my customers use Macs and only about half of those have
>systems powerful enough to retrieve PDF files over the web. That leave
>about 90 percent of my customers unserved by this approach.
>My $ 0.02. Joe
The point that you raise here goes to the heart of a lot of decisions that
must be made before starting out to design a web site. Boiled down to its
bare essentials, it addresses the first two questions which every
communicator (oral or written) must ask themself before preparing their work:
1) What is the makeup of my target audience?
2) How will they perceive (in this case, see on their monitors) what I am
going to present?
In your case, it's a platform issue. Do you create the site for the 80% and
risk losing the 20%? Do you write for both platforms? Budget and time
constraints will play a significant role in the second decision.
In other situations, you might have to decide whether to go with a graphical
site, with a text-only site, or with a combined site with some or all pages
mirrored for both text-capable and text-impaired browsers. Now why would
anyone choose a text-only solution? What if the bulk of your audience
conisisted of college professors who were receiving their Internet access
through old non-graphics web servers ported straight out of Bitnet with only
minimal bandwidth?
The same questions must be asked all over again with regard to using forms,
frames, animation and a host of other items that are not handled well (if at
all) by certain browsers. What percentage of my aduience uses browsers that
can deal with this feature? Am I willing to create something that the
remaining percentage will not see to best advantage? Am I (read this: "Is my
boss or client...") willing to put in the additional effort to mirror part
or all of the site to accommodate the differences?
Easy choices? No. But definitely part of the thought process that musy
preceed the development of any masterpiece of technical communication.
Shalom,
Shmuel
======================
Shmuel Ben-Artzi
sba -at- netmedia -dot- net -dot- il
======================
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-