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: One (1) question about odd number notation From:"Parks, Beverly L." <parksb -at- HUACHUCA-EMH7 -dot- ARMY -dot- MIL> Date:Mon, 9 Sep 1996 09:12:00 MST
As far as where it came from, I think you answered your own question: it
comes from legal documents; more specifically, contracts. (At least this
is what I learned the last time this topic came up.)
IMO, it's ugly and unnecessary. Ax it. 8-)
Bev Parks
parksb -at- huachuca-emh7 -dot- army -dot- mil
= = = = = = =
James Lockard, norton -at- mcs -dot- net, wrote:
>>
I recently started a new project in which I'm supposed to create an
online
version of an employee handbook. One of the issues I'm dealing with is
this
odd sort of number notation I've seen in legal documents where, after
each
number is written out, the numeral appears in parentheses.
For example, the handbook reads something like, "Full-time, regular
employees are granted three (3) personal days each year."
What's up with that? I cannot think of any solid reason for that
technique.
Is there any reason I _should_ keep that system?
<<
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-
