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.
My view is pretty much the opposite. I deny all knowledge of the
advanced techniques using SEQ fields and so on that some people use to
kludge Word into a semi-usable documentation authoring tool.
Using Word as the primary authoring tool for technical documentation
is a false economy. It's a safe bet that any company that does has
made many other false economies. That means that workplace suck in
many other ways, most of which you can learn about from reading
Dilbert. I would never apply for a job where Word is the primary tool
unless the were looking for someone to migrate to a professional
Having to convert a PDF to editable source is typically another sign
of an out-of-control company you'd be better off not working for,
unless they know they've made a mess and are hiring you to clean it
On Fri, Jun 26, 2015 at 11:11 AM, Chris Morton <salt -dot- morton -at- gmail -dot- com> wrote:
> First, become an expert in MS Word. Know everything there is to know about
> creating, using, and (most importantly) fixing styles. Learn all you can
> about Word's replaceable variables. The bulk of my work today
> is reworking user manuals that were incorrectly formatted from the get-go.
> Ping me and I'll tell you more. Related to that, know how to take a user
> manual from PDF to Word and back again, discovering all of
> the pitfalls along the way.
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW