Re: where to hyphenate: non-native-English-speaking ?

[dick -at- rlhamilton -dot- net]

Good point. I didnât think of that connection. So, really, my suggestion changes your intended meaning. Though it does highlight the importance hyphens in reducing ambiguity.

I agree with you; a rewrite is better than a hyphenated blob.

Richard
-------
XML Press
XML for Technical Communicators
http://xmlpress.net
hamilton -at- xmlpress -dot- net



> On Feb 23, 2017, at 16:31, Monique Semp <monique -dot- semp -at- earthlink -dot- net> wrote:
> 
>> I would go with two and a comma, that is: "non-native, English-speaking development team.â
> 
> Hmm... the problem is that it loses the link between "native" and "English". That is, I'm a native-English speaker. Ah, but there it is (maybe): no hyphen between "English" and "speaker". (I did look at Chicago, but got all turned around with references to open and closed compound nouns.) So maybe it's "non<emdash>native-English speaking development team"? But that makes it seem as if the team is a "speaking development" team, which makes no sense.
> 
> I guess the solution is to totally rewrite.
> 

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.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-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives