RE: Naming NAME fields

Subject: RE: Naming NAME fields
From: mlist -at- safenet-inc -dot- com
To: DGoldstein -at- riverainmedical -dot- com, techwr-l -at- lists -dot- techwr-l -dot- com
Date: Wed, 8 Nov 2006 13:17:20 -0500

Dan Goldstein [mailto:DGoldstein -at- riverainmedical -dot- com]
> Only if you check whether _your_ users more easily identify
> "Given Name
> and Family Name" than "First Name and Last Name." Otherwise, it's just
> Design By Assumption.
> > -----Original Message-----
> > From: mlist
> >
> > ... wouldn't it be better to differentiate names by "Family
> Name" and
> > "Given Name(s)" instead of the rather provincial "First Name" "Last
> > Name"?

Yes.... and the assumption is that "First Name" and "Last Name"
are _absolutely_ wrong for a couple of billion people on this
planet, significant numbers of whom have emigrated to your
country and to other countries where you might be selling
your product. My friend Chu Yin Man is bright enough to
figure out either one (being second-generation and all),
but his barely-english-speaking relatives would read
_your_ form literally, and type "Chu" (their family name)
in your "First Name" field, and "Man" in your "Last Name" field,
and your customers would have all their minimum-wage, script-reading,
support people trying to contact "Mr. Man" or "Mrs. Man".

How well do you react when somebody phones saying:
"I'd like to speak to Mr. Dan, please"?

Meanwhile, very few cultures do not use family names. If
you know somebody wants the name of your family in one field,
you can probably figure out that one of your other names
(picked by Mom and Dad to differentiate you from your brother
Daryl and your other brother Daryl...) should go into
the "Given Name" field, or at least you'll consider asking
somebody. Contrast with "First" and "Last" which you might
not question. Obviously, "Chu" (family name) is "First",
and "Yin Man" (given name) is "Last"... but only later will
some clerk (at the business that's using your software) choke
on that input.

I admit that you could be perfectly correct in your contention,
but I'd like to examine your reasoning, please.


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.

WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!

Easily create HTML or Microsoft Word content and convert to any popular Help file format or printed documentation. Learn more at

You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.


Previous by Author: Naming NAME fields (was RE: Coordinating Field Defs and Procedura l Info
Next by Author: RE: What tech writers "do"
Previous by Thread: Re: Portfolio Packaging--sample
Next by Thread: RE: Naming NAME fields

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

Sponsored Ads