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: Where to line=break a slash? From:"Butler, Darren J CTR USAF AFMC 584 CBSS/GBHAC" <Darren -dot- Butler -dot- ctr -at- Robins -dot- af -dot- mil> To:"Tech Whirlers" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 14 Jul 2008 09:04:38 -0400
All,
I should have indicated that this is for a table column title vice a
pathname or link. However, I also run into the same dilemma with
pathnames, so thanx to Peter and Chris.
I often learn more than I ask from the list.
Blessings,
Darren
-----Original Message-----
From: Peter Neilson [mailto:neilson -at- windstream -dot- net]
Sent: Friday, July 11, 2008 1:42 PM
To: Butler, Darren J CTR USAF AFMC 584 CBSS/GBHAC
Cc: Tech Whirlers
Subject: Re: Where to line=break a slash?
Butler, Darren J CTR USAF AFMC 584 CBSS/GBHAC wrote:
> Which of the following would be correct - and why?
> Doo-Wa-Diddy/Diddy-Dum
> /Diddy-Doo
> --OR-
> Doo-Wa-Diddy/Diddy-Dum/
> Diddy-Doo
Both are wrong. Both break the pathname. Your best bet is to include an
explanatory note, viz.:
"Because our corporate documentation standards provide insufficient
space to show the full pathname on one line, it is shown on two lines.
Enter it all on one line, and please tell our company president that you
would like a larger documentation format or shorter pathnames."
Oops, you're Air Force, and the standards all come from somewhere
inaccessible even to generals.
Hmmm. Perhaps you'd best leave out the editorializing altogether.
Oh, and I'm nearly certain that there is a mil spec somewhere that
covers the situation. You just haven't found it.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-