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.
Does anyone have recommendations for sources of information on what tech writers think are, or should be, the "right" ways to make screen captures and include them in technical documentation?
We use screen caps a lot where I work, but it's pretty freeform. There's no commonality in the software, in how images are named or stored, in how they are presented in the documents...It's every man for himself. I've been tasked in trying to find if there are any commonly accepted practices.
I am NOT interested in
- Copyright issues
- Using screen caps as court evidence
- Concerns about securing against attempts by hackers to make remote screen captures
I've done Google searches and these things appear to take up the large majority of Web articles about screen captures. None of them are relevant to me.
Arguments over which software tool may be informative, but the ones I've read so far seem to be based mainly on economics, rather than technical viability.
Any suggestions would be much appreciated.
ÂÂÂÂ Keith Hood
PS No, I'm not really sure why I was asked to do this. To the best of my knowledge, the current looseness of our "procedures" has never caused any problems.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com
