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.
It's just the way people who do renderings talk.
Repeated renders if the same image with trivial
changes are commonly referred to as "rerenders"
(or worse, depending on whether one is trying
to exercise restraint).
----- Original Message -----
From: "Boudreaux, Madelyn (GE Healthcare,consultant)"
<Madelyn -dot- Boudreaux -at- ge -dot- com>
> But then, why do you need to RE-render? Isn't every rendering a
> step and a complete rendering? Why not use "render again," or "render
> second time," or just "render" for the subsequent renderings?
ComponentOne Doc-To-Help gives you everything you need to author and
publish quality Help, Web, and print content. Perfect for technical
authors, developers, and policy writers. Download a FREE trial. http://www.componentone.com/DocToHelp/
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-