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: Standards on Using Graphics, Screen Captures, Illustrations, What-have-you In Doc
Subject:Re: Standards on Using Graphics, Screen Captures, Illustrations, What-have-you In Doc From:Chris Morton <salt -dot- morton -at- gmail -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 2 Nov 2018 16:07:02 -0400
I thought the MS guide specified whether an SS should appear before or
after its written instruction.
Anyway, I always crop shots so as to focus on the item being discussed.
Sometimes this means overlaying the cropped, enlarged, sectional SS over a
small full screen image that provides context. This is a sort of "exploded
view." I might add guidelines from the corners of the exploded view to
indicate relative positioning.
Other times I might simply crop the fullscreen image so as to focus the
reader's attention on a particular location.
I always attempted to keep each SS proportionately sized with respect to
one another.
On Fri, Nov 2, 2018 at 3:59 PM Robert Lauriston <robert -at- lauriston -dot- com>
wrote:
> That doesn't say anything about screen shots except that "screenshot"
> is one word.
>
> The old Microsoft Press style guide doesn't, either, except to note a
> couple of document types where screen shots might be appropriate.
>
> On Fri, Nov 2, 2018 at 12:49 PM Chris Morton <chris -at- isntthatwrite -dot- com>
> wrote:
> >
> > Maybe https://docs.microsoft.com/en-us/style-guide/welcome/oking for
> the archived Techwr-l email discussions? Search our public email archives
> @ http://techwr-l.com/archives
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Visit TechWhirl for the latest on content technology, content strategy and
> content development | https://techwhirl.com
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as salt -dot- morton -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com