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:Upper/lower case in heading From:John Posada <jposada01 -at- yahoo -dot- com> To:"List,Techwriter" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 27 Jun 2006 08:30:29 -0700 (PDT)
Hi, guys...assuming we cannot change our style rule to sentence case
and it outside of consideration at this point, what convention do you
follow to justify your actions when you make a change to someone
elses content from the perspective of case in headings?
I'm checking the content of another writer's documnt and it appears
he applies case in a random manner (but then maybe I just don't see
the logic). For instance, following are some of the headings in a
Release Note:
-Broker Might Be Inadvertently Uninstalled
-Installation Directories May not Contain Spaces
-VPN Maps do not Increment and Decrement Hops
It seems if the first one uses "Might Be", the next example should be
"May Not", not "May not", and if the second example is "May not",
isn't "do not" inconsistent?
My question...if I tell him to change any of them, and he says Why?,
what rule do I quote?
John Posada
Senior Technical Writer
"So long and thanks for all the fish."
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l