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.
You don't find that a comments column is a big drain on available space, in a table?
Or, similarly, that it can result in lots of vacant cells that constitute non-helpful white-space?
I like the artful use of whitespace on a page of text or text-and-graphics, to enhance the readability, but if more than half the cells in a column are empty, I wonder why the author didn't just use asterisks and a couple of footnotes.
-----Original Message-----
From: Scott Bulloch
Sent: November-08-13 12:41 PM
Cc: TECHWR-L Writing
Subject: Re: Footnotes - acceptable in technical documentation?
At my company, we don't use footnotes in regular instructional text. Our practice for stuff like that is to indent a note icon (like a light bulb for tips or a yield sign for cautions) and a paragraph or so of text.
As far as tables go, I have seen table footnotes, but lately, the practice has been more toward putting such information in a Comments cell in the row.
On Fri, Nov 8, 2013 at 9:10 AM, Robert Lauriston <robert -at- lauriston -dot- com>wrote:
> Looking at the MS Manual of Style 4, there are a few references to
> table footnotes, no mention of regular footnotes.
>
> There's also one reference that seems to presume the writer is using
> Word to edit WinHelp source: "Also, cross-references (See and See
> also) are limited to normal keywords that jump directly to the topic
> that contains the K (keyword) footnote with that keyword."
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.