RE: Documenting a buggy feature (was: RE: techwr-l digest: April 30, 2002)

Subject: RE: Documenting a buggy feature (was: RE: techwr-l digest: April 30, 2002)
From: "Stevenson, Rebecca" <Rebecca -dot- Stevenson -at- workscape -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 1 May 2002 10:38:02 -0400


The approach I've seen in my previous positions was to document the way it's supposed to work, and then use release notes to document the workaround if one is needed.

Rebecca


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Are you using Doc-to-Help or ForeHelp? Switch to RoboHelp for Word for $249
or to RoboHelp Office for only $499. Get the PC Magazine five-star rated
Help authoring tool for less! Go to http://www.ehelp.com/techwr

Free copy of ARTS PDF Tools when you register for the PDF
Conference by April 30. Leading-Edge Practices for Enterprise
& Government, June 3-5, Bethesda,MD. www.PDFConference.com

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.


Previous by Author: Fee-based recruiters
Next by Author: Man pages Was RE: Structure for GUI & Command Line Input Doc
Previous by Thread: Documenting a buggy feature (was: RE: techwr-l digest: April 30, 2002)
Next by Thread: Documenting a buggy feature (was RE: techwr-l digest: April 30, 2002)


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


Sponsored Ads