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.
Robert Lauriston suggested:
>
> "If your device works perfectly, but your customers can't use it
> correctly ...": in other words, you tested the device to validate its
> usability and it failed, right?
>
> Why not just use the standard English "not validated" or "not
> yet validated"?
And, as in my industry, when there are some that we just don't bother to validate? Or rather, we don't go to the time (from several months, to more than a year) and considerable expense of submitting them to third-party labs that validate them against a government standard...?
They're still "validated" by Engineering Test group (formerly called... wait for it... Product Validation), and also by QA before they ship, but they might be an interim or niche version and thus not worth the trouble to get 'em certified as validated against the government standard.
"Validated and not validated HSMs are functionally identical and are designed and built to the same performance and security standards." I dunno. Sounds clunky to me.
The "not validated" could also become scan-error-inducing if it occurred at an inconvenient physical location on a page.
I wonder how many people would ever be confused by "un" in front of a word that they knew.
Is it that I only imagine "un" to be a standard, common English prefix, well-known for its meaning and its effect on any word it precedes?
- Kevin
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.
Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices. http://www.doctohelp.com/SuperPages/Webcasts/
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
