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.
Subject:RE: Docs on Tape From:John Posada <JPosada -at- book -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 26 Jun 2003 14:37:00 -0400
A good idea doesn't have to apply to every condition. If not appropriate,
don't do it. I can think of a large number of sections of my document where
this makes sense and a large number where it doesn't.
I have 3-5 pages at the beginning of each section describing the technology
of that section. I can easily see a 5 page description of database
replication being spoken and listened to.
John Posada
> Thoughts?
"Code example 3-4 illustrates this principle. Example 3-4: static
void main MyClass open paren string open bracket close bracket argv
close paren open curly bracket int counter equals zero semicolon...."
RoboHelp Studio maximizes your Help authoring power by combining
RoboHelp Office and RoboDemo, so you can easily create professional
Help systems that feature interactive tutorials and demos.
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.