RE: too narrow or too-narrow?

Subject: RE: too narrow or too-narrow?
From: "Mike McCallister" <mike -dot- mccallister -at- pkware -dot- com>
To: <dvora -at- tech-challenged -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 19 Jan 2010 15:43:01 -0600

If forced to choose, I'd agree with the client (hyphen).

Even better to my mind is the ever-popular "recasting so no one pauses":
"This slot is too narrow for layer 9-16" or "This slot on layer 9-16 is
too narrow."



Mike McCallister
Document Architect
PKWARE, Inc.

-----Original Message-----
From: techwr-l-bounces+mike -dot- mccallister=pkware -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+mike -dot- mccallister=pkware -dot- com -at- lists -dot- techwr-l -dot- com]
On Behalf Of Deborah Hemstreet
Sent: Tuesday, January 19, 2010 3:33 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: too narrow or too-narrow?

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 archive -at- web -dot- techwr-l -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/archive%40web.techwr-l.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


Follow-Ups:

References:
A Better Technical Writer/Communicator Library: From: david hendler
Re: A Better Technical Writer/Communicator Library: From: Paul Goble
RE: A Better Technical Writer/Communicator Library: From: Janoff, Steve
Re: A Better Technical Writer/Communicator Library: From: Janet Swisher
RE: A Better Technical Writer/Communicator Library: From: Janoff, Steve
too narrow or too-narrow?: From: Deborah Hemstreet

Previous by Author: RE: What do you do when you don't have anyone with the time to reviewand edit your docs
Next by Author: Tech doc requirements for European markets
Previous by Thread: too narrow or too-narrow?
Next by Thread: RE: too narrow or too-narrow?


What this post helpful? Share it with friends and colleagues:


Sponsored Ads