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: Ampersands in TOC and headers? From:"Leonard C. Porrello" <Leonard -dot- Porrello -at- SoleraTec -dot- com> To:"Bill Swallow" <techcommdood -at- gmail -dot- com> Date:Tue, 9 Feb 2010 09:12:53 -0800
I am responsible for style, so whatever I say pretty much goes. This
isn't to say that style is capricious. It just means that we define what
styles we'll use based on what best fits what we are communicating. The
thing I want to avoid is taking license in a way that could offend a
significant number of readers. For example, I could see reasons for
using a initial cap after a semi-colon, but I wouldn't do so as some
people would think it was done out of ignorance. It seems to me that my
use of ampersands, on the other hand, could go either way.
Leonard
-----Original Message-----
From: Bill Swallow [mailto:techcommdood -at- gmail -dot- com]
Sent: Tuesday, February 09, 2010 8:47 AM
To: Leonard C. Porrello
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Ampersands in TOC and headers?
I dunno. What does the style you're using dictate? What does your
style guide say?
On Tue, Feb 9, 2010 at 11:41 AM, Leonard C. Porrello
<Leonard -dot- Porrello -at- soleratec -dot- com> wrote:
>
> My docs feature some relatively long, task oriented titles. To
minimize
> the length of TOC entries, I've used ampersands in the way they are
used
> in newspaper headlines.
>
> Is this problematic from a style perspective?
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-