At 11:31 -0600 10/8/06, Tammy.VanBoening at jeppesen.com wrote:
>My editor has removed the "if necessary" phrase saying that they are extra
>words and that the user will eventually figure out that sometimes they
>don't need to open the tab - that it is already open. This seems
>counter-productive
At 11:31 -0600 10/8/06, [EMAIL PROTECTED] wrote:
>My editor has removed the "if necessary" phrase saying that they are extra
>words and that the user will eventually figure out that sometimes they
>don't need to open the tab - that it is already open. This seems
>counter-productive to me. We don't
Thanks for all of the responses. They were all over the board, from
keeping the wording to getting rid of it, to changing the whole layout of
the intro. to each procedure. Ultimately, the sugesstion I liked best was
this:
1. Open application by double-clicking the icon in the System
Tray.
2.
Another option is to include, in your preliminary sentence, a
crossref/link to the basic navigational steps they need to perform to
get to the tab.
That way the nav info's available for the novices and not in the way
for the more experienced.
Art
On 8/10/06, Tammy.VanBoening at jeppesen.com
wr
Thanks for all of the responses. They were all over the board, from
keeping the wording to getting rid of it, to changing the whole layout of
the intro. to each procedure. Ultimately, the sugesstion I liked best was
this:
1. Open application by double-clicking the icon in the System
Tray.
2.
.com
Date: Thursday, August 10, 2006 1:32 pm
Subject: OT: Writing/editing style
To: framers at frameusers.com
> Again, since there are so many veteran writers on this and who
> have
> learned through the years to maneuver their way through the
> editing
> process:
>
> I am
Boening at jeppesen.com"
>CC: framers at frameusers.com
>Subject: Re: OT: Writing/editing style
>Date: Thu, 10 Aug 2006 13:40:06 -0400
>
>I'd probably do away with your first two steps entirely and preface
>the actual instructions with something like:
>"On (or From) the [appl
I'd probably do away with your first two steps entirely and preface
the actual instructions with something like:
"On (or From) the [application's] [foobar] tab:
1. Do this...
2. Do that...
3. Do the other thing ... "
So that you can just jump into the procedure. If you've done a decent
job identif
Hi, Tammy:
Have you tried posting to TECHWR-L also?
My opinion is that good writing won't substitute for a poor design.
One approach might be to mention that the tab selection is "sticky" -
that is, the last-used tab appears when opening from the tray icon.
Many good applications provide users
Another option is to include, in your preliminary sentence, a
crossref/link to the basic navigational steps they need to perform to
get to the tab.
That way the nav info's available for the novices and not in the way
for the more experienced.
Art
On 8/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]
Boening
Senior Technical Writer
Jeppesen Sanderson, Inc.
303-328-4420
tammy.vanboening at jeppesen.com
"Combs, Richard"
Sent by:
framers-bounces+tammy.vanboening=jeppesen.com at lists.frameusers.com
08/10/2006 12:09 PM
To
cc
Subject
RE: OT: Writing/editing style
Fred R
Fred Ridder wrote:
> Focus on essential steps (accomplishing the task at hand).
> Assume automatic actions (like basic navigation).
> Eliminate unnecessary words.
I'm with Art and Fred. Unless you're writing for complete computer
novices, don't describe _how_ to switch to another application or
Again, since there are so many veteran writers on this and who have
learned through the years to maneuver their way through the editing
process:
I am writing to a major application, that when launched, results in three
other applications being launched and running continuously in the
backgroun
Boening
Senior Technical Writer
Jeppesen Sanderson, Inc.
303-328-4420
[EMAIL PROTECTED]
"Combs, Richard" <[EMAIL PROTECTED]>
Sent by:
[EMAIL PROTECTED]
08/10/2006 12:09 PM
To
cc
Subject
RE: OT: Writing/editing style
Fred Ridder wrote:
> Focus on essential ste
day, August 10, 2006 1:32 pm
Subject: OT: Writing/editing style
To: framers@frameusers.com
> Again, since there are so many veteran writers on this and who
> have
> learned through the years to maneuver their way through the
> editing
> process:
>
> I am writing t
Hi, Tammy:
Have you tried posting to TECHWR-L also?
My opinion is that good writing won't substitute for a poor design.
One approach might be to mention that the tab selection is "sticky" -
that is, the last-used tab appears when opening from the tray icon.
Many good applications provide use
Fred Ridder wrote:
> Focus on essential steps (accomplishing the task at hand).
> Assume automatic actions (like basic navigation).
> Eliminate unnecessary words.
I'm with Art and Fred. Unless you're writing for complete computer
novices, don't describe _how_ to switch to another application or
I'd probably do away with your first two steps entirely and preface
the actual instructions with something like:
"On (or From) the [application's] [foobar] tab:
1. Do this...
2. Do that...
3. Do the other thing ... "
So that you can just jump into the procedure. If you've done a decent
job identi
[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
CC: framers@frameusers.com
Subject: Re: OT: Writing/editing style
Date: Thu, 10 Aug 2006 13:40:06 -0400
I'd probably do away with your first two steps entirely and preface
the actual instructions with something like:
"On (or From) the [appl
Again, since there are so many veteran writers on this and who have
learned through the years to maneuver their way through the editing
process:
I am writing to a major application, that when launched, results in three
other applications being launched and running continuously in the
backgroun
20 matches
Mail list logo
