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.
>It has been gratifying to see that my question regarding alternative
titles for technical writers spawned quite a range of discussion.
If it's not too late, and you are up for a little tongue-in-cheek, I
have always thought that sentence engineer or paragraph architect
were pretty good.
>In the meantime, I have a question regarding the citing of sources.
What are everyone's thoughts on this matter?
General Rule No. 1. For ordinary user manuals, be as informal as
possible, rolling the citation into your sentence. For a technical
reference or some kind of document where citing sources adds to your
credibility, go for footnotes either at the bottom of the page or end
of the chapter.
General Rule No. 2. If you are dealing with long titles that would
interrupt the flow of your text if you included them, go for
footnotes. You might have a reference list in the back, numbering
each reference work as appropriate in the text. William Horton in
Designing and Writing Online Documentation does this.
General Rule No. 3. Always consider your readers. Different
disciplines have different ways of handling this sort of thing. Your
concern should be to figure out what system, if any, your readers may
be used to. If none, then go for concerns such as usefulness,
helpfulness, readability, usability, and credibility.
bsullivan -at- deltecpower -dot- com
San Diego, California