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.
You can also initialize the product in your lab, fiddle with it for a while, then perform factory-reset and ship it off to its destination in ... !initialized! state.
I guess "wish" is one of those regional things, similar to the situation on this list - some years ago - where several people argued vociferously against the use of the PERFECTLY ACCEPTABLE "appear" in techdocs, claiming that the only inference they could garner from "appear" or "appears" was.... magic... (insert shimmer-tone and Theremin glissando here).
> -----Original Message-----
> From: James Leatherwood [mailto:JLeatherwood -at- aflac -dot- com]
> Sent: October-11-12 8:11 AM
> To: McLauchlan, Kevin; techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: RE: Usage question - "... un-initialized state" or "... an
> uninitialized state"
>
> You can initialize the product before delivery, or defer initialization to
> the end-user.
>
> Initialization prior to delivery is optional.
>
> Why emphasize the "un?"
>
> And FWIW I agree with avoiding "wish." People wish they could do
> lots of things with software that developers don't bake into the
> system.
>
> James Leatherwood
>
>
> -----Original Message-----
> From: McLauchlan, Kevin [mailto:Kevin -dot- McLauchlan -at- safenet-
> inc.com]
> Sent: Wednesday, October 10, 2012 11:32 AM
> To: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: Usage question - "... un-initialized state" or "... an
> uninitialized state"
>
> The statement in the docs is: "You might wish to deliver the product in
> un-initialized state."
>
> One reviewer wants that to say: "You might wish to deliver the
> product in AN un-initialized state."
>
> My objection to that version is that it suggests/implies that there is
> more than one un-initialized state.
>
> With respect to initialization, there are two states - initialized and un-
> initialized. There are no sub-categories under un-initialized, and no
> grey areas. It is or it ain't.
>
> What say you language mavens?
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.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.
