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.
Re: For references or directives, do you say where/why and then what/how, or vice versa?
Subject:Re: For references or directives, do you say where/why and then what/how, or vice versa? From:John Allred <john2 -at- allrednet -dot- com> To:Lin Sims <ljsims -dot- ml -at- gmail -dot- com> Date:Fri, 17 Aug 2018 10:43:03 -0500
The use of numbers for callouts is a long-standing practice that I agree with. Yes, âsome peopleâ will fail to understand the simplest of instructions. Can that be remedied through changing conventions?
On Aug 17, 2018, at 9:42 AM, Lin Sims <ljsims -dot- ml -at- gmail -dot- com> wrote:
>
> ...
> My current preference (subject to change with better data) is to use
> letters as callouts on the graphic and refer the reader to that callout
> letter. This was after much grumbling on my part, since my preference is to
> use numbers, not letters, but the argument that the reader could interpret
> the callout number as being associated with a numbered step was enough to
> convince me to change my ways.
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
