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.
Use the darned hyphen! The poor little thing suffers from neglect,
but is so useful in a few situations that we must not lose it entirely,
lest we become unionized (or unionised) when we needed to be un-ionized.
Janice Gelb and many others have commented on Sonja McShane's plight:
>> For now, after much searching in archives and the Internet, I need to
>> know definitively if I should hyphenate "command-line utility". I know
>> the compound modifier 'command line' can't be misinterpreted if it's not
>> hyphenated, but I really, really feel the need to hyphenate it anyway.
Janice:
> As others have said, this sort of question rarely
> has a definitive answer but as a data point, the
> Sun style guide still specifically calls for "command
> line" to be hyphenated as a modifier in line with our
> general rule about hyphenating compound modifiers.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
