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: Missing the point From:"Goldstein, Dan" <DGoldstein -at- DeusTech -dot- com> To:"TECHWR-L (E-mail)" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 21 Jan 2004 11:19:23 -0500
It isn't "a bad thing" that the TOC picks up manual formatting when you want
it to, as in the example you cited.
However, if you don't want your formatting picked up by the TOC, the proper
solution is to use character styles. I thought it was funny that the MS KB
suggested three separate workarounds, without even mentioning character
styles.
Dan Goldstein
> -----Original Message-----
> From: dmbrown -at- brown-inc -dot- com
> Sent: Wednesday, January 21, 2004 11:08 AM
> To: TECHWR-L
> Subject: Re: Missing the point
>
> Goldstein, Dan wrote:
> >
> > Microsoft...fails to note the obvious solution:
> > Don't use manual formatting! Geez...
>
> It's very useful to have manual formatting carried into the TOC.
>
> Suppose, for example, that your style guide calls for command
> names to be
> set in a monospace font, and you want the TOC to be consistent. This
> behavior saves you having to apply the font change to every
> occurrence of a
> command name in the TOC, every time you rebuild the TOC.
>
> How can that be a bad thing? Geez, indeed.
>
> --David
>
