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.
"Default preferences" is not redundant. In our app, for example, we have
user preferences that users can set to control how the application
behaves. The original value for each preference, before they set
anything, is "the default".
So, the difference is that preferences are attributes and defaults are
values.
Chris
-----Original Message-----
From: techwr-l-bounces+cvickery=arenasolutions -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+cvickery=arenasolutions -dot- com -at- lists -dot- techwr-l -dot- com]
On Behalf Of Debra Graham
Sent: Tuesday, July 10, 2007 12:43 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Preferences versus defaults
Dear Techwhirlers-
I've not had occasion to reflect on the differences between preferences
and
defaults, until today when I was asked to create a job aid on "setting
default preferences on the Auto Carry Forward Config page."
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").
So I was wondering if there was any documented usage guidelines or even
any
consensus. Now, I know that asking Techwhirlers to come to a consensus
is
crazy but I was hoping to get *some* feedback on usage. (BTW, I did do
quick Google and techwr-l searches.) Any help out there?
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 cvickery -at- arenasolutions -dot- com -dot-
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-