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: Preferences versus defaults From:Amy Gale <amyg -at- grammatech -dot- com> To:Debra Graham <debra -dot- graham -at- gmail -dot- com> Date:Tue, 10 Jul 2007 16:07:47 -0400
Debra Graham wrote:
>[...]
>
>
>The term "default preferences" seems redundant to me and I began wondering
>whether there was a difference between a default and a preference. At
>first, I thought perhaps one applies to behavior and the other applies to
>values? But that distinction didn't seem to hold—default behavior and
>default values both make sense to me. Then I started thinking about
>options, settings, and so forth, and quickly became overwhelmed (well, not
>really overwhelmed but realized that I didn't have time to explore the
>various "options").
>
>[...]
>
It's easy to get tied up in mental knots in this area, isn't it? I feel
your pain :)
In some systems I see, there are two levels of "defaultage":
1) if you don't specify a value for something (a build tag, say), it
will "default" to the value stored in the relevant preference.
2) if you haven't specifically set the value for said preference, it
will have some "default" value (for example, the factory setting).
I try to keep "default" for situation 2, and use verbs like "use" and
"apply" to describe what happens in situation 1. This helps to mark the
semantic distinction and reduces the density of "defaults" in the text.
Of course, now that I have made this separation claim it will doubtless
be mere hours before I run into a past example of myself doing nothing
of the sort...
Amy "the default default defaults to the default" Gale
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-