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:RE: There must be some kind of standard.... From:Andrew Warren <awarren -at- synaptics -dot- com> To:'jopakent' <jopakent -at- comcast -dot- net>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 24 Feb 2010 15:32:09 -0800
jopakent wrote:
> "The purpose of this procedure is to establish the
> responsibilities and requirements for controlling Documents."
>
> I run into this kind of writing so frequently here, that I'm beginning
> to wonder if there might be some basis for it. It seems like there is
> some kind of guideline that says: "if something is important or
> significant, capitalize it."
First of all, everyone knows that the rule is "If it's important or significant, surround it with quotation marks."
Second, no. Unless the word's being used as a proper noun -- is "Documents" the name of a department? Is it being used not as the dictionary defines it, but rather as an identifier for a particular type of computer file or something? -- it doesn't get capitalized in English.
-Andrew
=== Andrew Warren - awarren -at- synaptics -dot- com
=== Synaptics, Inc - Santa Clara, CA
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
