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: too narrow or too-narrow? From:Susan W Gallagher <susanwg -at- gmail -dot- com> To:dvora -at- tech-challenged -dot- com Date:Tue, 19 Jan 2010 13:47:57 -0800
The rule is, use a hyphen to join two or more words serving as a single
adjective, so...
one-day seminar
chocolate-covered peanuts
too-narrow slot
Some grammar books say the hyphen is not necessary when the first word of
the compound adjective is an adverb, so would not hyphenate "well known
expert" but other books say to.
HTH!
-Sue Gallagher
On Tue, Jan 19, 2010 at 1:33 PM, Deborah Hemstreet <
dvora -at- tech-challenged -dot- com> wrote:
> Hi All,
>
> I have a caption which reads: "A too narrow slot on layer 9-16"
>
> The question: should this be written as
>
> 1. A too narrow slot on...
>
> or
>
> 2. A too-narrow slot on...
>
> My client says that since too modifies narrow it needs to be hyphenated. I
> admit, these nuances in grammar drive me nuts. Which is right?
>
> Thanks!
>
> Deborah
>http://www.tech-challenged.com
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Are you looking for one documentation tool that does it all? Author,
> build, test, and publish your Help files with just one easy-to-use tool.
> Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at:
>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 susanwg -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
>http://lists.techwr-l.com/mailman/options/techwr-l/susanwg%40gmail.com
>
>
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/ for more resources and info.
>
> Please move off-topic discussions to the Chat list, at:
>http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat
>
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: 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-