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.
>It may not be a tie-breaker today, but since Microsoft has announced
>that, as of next year, they are standardizing on HTML for help
The immediate problem is that there is no HTML upon which MS can
standardize. The major HTML dialects being used are Netscape's
NHTML 2.0 and MS's MSHTML 3.0. Lots of lesser known dialects
are also in use. In the meantime, hardly anyone uses the actual
HTML standards (2.0 and 3.0).
Thus, MS has to develop yet another version of HTML to support Winhelp.
Believe me, this is a Big Job (about the same as redeveloping RTF from
scratch). And the Web is moving so quickly that by the time MS is done
that (pick one or all):
o MS succeeds only in splintering HTML further
o Everyone may have standardized on something else, ignoring MS
o Everyone starts using browsers, so DTP itself is obsolete
(probably not, but who knows?)
In other words, working on the Web (and the Web itself) is a big
roll of the dice. No one really knows what's happening now, much
less what's going to happen next. In the meantime, MS shows no
sign of being able to dominate the Web. (Not that they're not trying.)
> I frequently bypass my Robo and work directly on the files.
This is a great idea.
David (The Man) Blyth
Technical Writer & Web Site Designer
The usual disclaimers apply - I don't speak for QUALCOMM, they don't speak