Re: Solution! RE: pushpins

Subject: Re: Solution! RE: pushpins
From: Sean Brierley <seanb_us -at- yahoo -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 1 Jul 2003 05:59:00 -0700 (PDT)

That's hillarious.

Okay, as long as it's the right basic language, we're
all set. Verbs? Got those--no worries about tense or
number, the reader will understand . . .. <g> The "Zog
like fire" approach to technical writing, cool.

In case of push-pin and pushpin, case is little
different than bite and byte. Yes. But, me say here
Microsoft term, here Webster term, here preferred term
of developer, is there reason to perfer one.
Understand, I use term "push pin," "push-pin," or
"pushpin" consistently but would like to be consistent
with third-party authority and group of peers, too.
(No need for variable, could use search and replace.
But why will I replace the term globally, anyway, if
it no matter?)

Me could say "dialogue box" and reader still
understand, but for American audience is there
preference for "dialog box"? Is not "dialog box"
preferable for American audience? Is difference

Now, fraction of font or whatever is not about
terminology. Maybe it about readability? Me no know.
Methinks there little difference in readability tween
10.5 and 10 point type, if that what you mean. Is
there third party authority with view on that? Or, is
this to do with making newsletter fit in required
number of pages? I say industry standard terminology
different issue than 10.5 versus 10 point type.

Me pick "pushpin" cos less typing.

Zog might be wrong tho.



--- David Castro <thetechwriter -at- yahoo -dot- com> wrote:
> Bruce Byfield wrote:
> > Wasn't it just last week that half the posters on
> the list were
> > belittling designers for worrying about a
> fractional different in font
> > size?


Create professional Help systems that feature interactive tutorials and
demos with all new RoboHelp Studio. More at

Mercer University's online MS Program in Technical Communication Management:
Preparing leaders of tomorrow's technical communication organizations today.
See or write George Hayhoe at hayhoe_g -at- mercer -dot- edu -dot-

You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit for more resources and info.


Re: Solution! RE: pushpins: From: David Castro

Previous by Author: OEM Documentation: Who retains the copyright?
Next by Author: Re: UML
Previous by Thread: Re: Solution! RE: pushpins
Next by Thread: Re: Solution! RE: pushpins

What this post helpful? Share it with friends and colleagues:

Sponsored Ads