documenting commands

Subject: documenting commands
From: "Kimberly McClintock" <kimberly -dot- mcclintock -at- openlogic -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Mon, 9 Apr 2007 12:15:36 -0600

Hey folks....

Wonder how you've seen commands so long they need to wrap to the next
line handled and what you're favorite way to solve this is. I've got a 6
page doc w/ dozens of commands, only one long enough to be a problem so
I'd rather not use a pre if I can avoid it 'cause I don't want to do
that for all the others.




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.

Now shipping: Help &amp; Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help &amp; Manual:

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

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 for more resources and info.


Previous by Author: classes
Next by Author: usage question: since/because
Previous by Thread: Run-in Style Index, in FrameMaker
Next by Thread: Re: documenting commands

What this post helpful? Share it with friends and colleagues:

Sponsored Ads