atw: Developer Access to Docs (was RE: Re: Duplicating material in procedures [SEC=UNCLASSIFIED])

I agree Arnold. I learnt a long time ago to NEVER give a developer access to
my documents. I give them PDF versions that only allow them to print.

They then have to hand back the document with their mark-ups or, using the
PDF as a reference, provide me with an ASCII or Word document with their
amendments.

Every-so-often though, I get caught when I help them out with THEIR
documents.

But such is life :)

Cheers,

Bruce Ashley
Principal Technical Writer
----------------------------------------------------------------------------
-----------------------------------
Preston Aviation Solutions Pty Ltd      Website:  http://www.preston.net
488 Victoria Street                     email: bashley@xxxxxxxxxxx
Richmond VIC 3121                       Ph:    +61 3 9428 8899
Australia                               Fax:   +61 3 9427 1969
----------------------------------------------------------------------------
-----------------------------------
Setting the standard in software solutions for the global aviation industry,
utilising advanced simulation, scheduling, optimisation and visualisation
technology.
A subsidiary of The Boeing Company




-----Original Message-----
From: austechwriter-bounce@xxxxxxxxxxxxx
[mailto:austechwriter-bounce@xxxxxxxxxxxxx]On Behalf Of Arnold Howard
Sent: Friday, 16 December 2005 1:06 AM
To: austechwriter@xxxxxxxxxxxxx
Subject: atw: Re: Duplicating material in procedures [SEC=UNCLASSIFIED]


Sometimes low-tech procedures are still the best. Have your developers make
corrections with pen on paper printouts. Not only will you preserve the
formatting of your document, but you will have the additional advantage of
quickly locating all their changes.

Arnold

From: "Melanie Kendell" <melanie.kendell@xxxxxxxxx>
On 15/12/05, Silcock, Howard DR <Howard.Silcock@xxxxxxxxxxxxxx> wrote:
>
> the developers may be working on the document again...
Ahhh, I see your problem now. Solution - give up :) Or shoot the developers.
Or shoot yourself.
Seriously though, there's no foolproof (or developer proof) method.


**************************************************
To post a message to austechwriter, send the message to
austechwriter@xxxxxxxxxxxxxx

To subscribe to austechwriter, send a message to
austechwriter-request@xxxxxxxxxxxxx with "subscribe" in the Subject field.

To unsubscribe, send a message to austechwriter-request@xxxxxxxxxxxxx with
"unsubscribe" in the Subject field.

To search the austechwriter archives, go to
www.freelists.org/archives/austechwriter

To contact the list administrator, send a message to
austechwriter-admins@xxxxxxxxxxxxx
**************************************************

**************************************************
To post a message to austechwriter, send the message to 
austechwriter@xxxxxxxxxxxxxx

To subscribe to austechwriter, send a message to 
austechwriter-request@xxxxxxxxxxxxx with "subscribe" in the Subject field.

To unsubscribe, send a message to austechwriter-request@xxxxxxxxxxxxx with 
"unsubscribe" in the Subject field.

To search the austechwriter archives, go to 
www.freelists.org/archives/austechwriter

To contact the list administrator, send a message to 
austechwriter-admins@xxxxxxxxxxxxx
**************************************************

Other related posts: