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: Spaced out From:"Dick Margulis " <margulis -at- mail -dot- fiam -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 28 Nov 2001 12:47:35 -0500
Alex,
I've seen the same thing. I'm sure many of us have. I usually just fix the damn thing (either using a macro or search/replace, depending on the context). It's easier than changing behavior of people who think they're too important to bother with that stuff.
However, if you have a person who seems willing to learn but is graphically clueless, try changing the margins or point size to make such a passage come out all funky and then print out a sample page to demonstrate what the problem is. Next, sit in front of your monitor with the developer and look at the document with markers turned on so the spaces are visible dots (or whatever). Point out the hanging indent styles you use; show how the indent controls work; show the same passage properly formatted. Usually, one such lesson will result in at least some improvement, and the person may even be sufficiently interested to come back to you for further help in the future. Ya never know.
Dick
"Alex Silbajoris" wrote:
>
>
>As I have been combing through some detail specification documents prepared
>by developers, I'm finding many instances of an odd behavior. I wonder if
>anyone can cofirm a hunch I have.
>
>The developers who populated these documents have the habit of using the
>space bar to advance the cursor to the next line, instead of hitting a hard
>return or a shift-enter combination. This puzzled me for months, but I think
>I may know why this habit seems to be so ingrained. Some of these documents
>have system screen shot facimilies, composed in monospace type, and the
>screen shots use spaces to position text. Perhaps these people simply use
>the same technique to compose a page of hanging-indent paragraphs made
>entirely of text and spaces, without a single return character on the page.
>(Of course, you can imagine what happens when the top paragraph is edited.)
>
>Has anyone else seen this as a cultural tradition among developers? Is
>there some tactful way to tell them they're keystroking like they're unaware
>the software can wrap lines?
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.