RE: too narrow or too-narrow?

[Keith Hood <klhra -at- yahoo -dot- com>]

I agree with Mike here, especially on the idea of rewriting the sentence. That protects you in the future by preventing nitpicking.


--- On Tue, 1/19/10, Mike McCallister <mike -dot- mccallister -at- pkware -dot- com> wrote:

> From: Mike McCallister <mike -dot- mccallister -at- pkware -dot- com>
> Subject: RE: too narrow or too-narrow?
> To: dvora -at- tech-challenged -dot- com, techwr-l -at- lists -dot- techwr-l -dot- com
> Date: Tuesday, January 19, 2010, 4:43 PM
> 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 klhra -at- yahoo -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/klhra%40yahoo.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- 

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