Re: Adobe Technical Communications Suite

Subject: Re: Adobe Technical Communications Suite
From: Bill Swallow <techcommdood -at- gmail -dot- com>
To: Robert Lauriston <robert -at- lauriston -dot- com>
Date: Wed, 6 Jan 2010 14:31:21 -0500

> I find it hard to believe that Adobe's product managers have ever
> spent much time talking with technical writers and documentation
> managers about our needs.

Really? You must not follow a lot of techcomm traffic outside this
listserv then. RJ (the TCS product manager) is highly visible and

> Help 2 is a requirement in certain development environments, I forget
> which (Visual Studio .NET?), but a company my old employer acquired
> had had to move some of their docs to it.

It's only for VS.NET, yes, but isn't a requirement for the technology.
It was never formally released as a format, and was only supported by
MS with the release of Sandcastle after the head developer (and only
remaining developer) for nDoc quit development (which he'd been doing
for free) after being harassed by too many people. Too bad, because he
was a nice guy who had a genuine interest in providing a solid code
documentation tool for C# developers.

> Same goes for Eclipse help. I switched my department from WebWorks to
> MIF2Go because it supported Eclipse.

Eclipse Help does have a market but it's a fairly small one (per the
most recent WritersUA Skills and Technologies survey). Unless you're
looking to cash in on a niche market, it doesn't make sense to devote
a ton of resources into development against a niche technology. Adobe
is a giant, and whether we think they're right or wrong, they will
look for the greatest bang for their development buck and will push
their own technologies whenever possible to continually grow their
adoption. It's the nature of the corporate game.

Bill Swallow

Twitter: @techcommdood

Available for contract and full time opportunities.

STC Ideas:

Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at:

Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at:

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Please move off-topic discussions to the Chat list, at:

Re: Adobe Technical Communications Suite: From: rstone75
Re: Adobe Technical Communications Suite: From: Robert Lauriston

Previous by Author: Re: Adobe Technical Communications Suite
Next by Author: Re: Adobe Technical Communications Suite
Previous by Thread: Re: Adobe Technical Communications Suite
Next by Thread: Re: Adobe Technical Communications Suite

What this post helpful? Share it with friends and colleagues:

Sponsored Ads