TechWhirl Sponsors

About TechWhirl

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.

I'm missing something here. A Web browser is not designed to improve on
Acrobat. They're designed to connect to the Internet (to other documents,
functions such email, news or ftp, or even full-scale applications).

IMHO, it seems like much of the debate has revolved around the appearance
of the document. What does it look like on the screen?

But Web pages aren't designed for appearance in the first place. HTML's
structure is designed to provide compatability between the multiple file
formats and appliations on the Internet.

Acrobat wins the appearance issue so easily that it's not worth debating.
But the real question is not appearance, but how to get reliable information
to the customer.

Browser proponents (myself included) contend only that a browser structure
and flexible file formats is _usually_ more important than appearance because:

o The customer gets what they need a lot faster

o The customer can link to other useful applications or functions
(not provided by Acrobat) without increasing overhead.

David (The Man) Blyth
Technical Writer & Web Site Designer
Qualcomm

The usual disclaimers apply - I don't speak for QUALCOMM, they don't speak
for me....