I've used VSS extensively for documentation, and found it quite acceptable. Makes life a lot easier when we're doing information development along the same model that is used for software development. Labelling documentation to match software versions ensured they always scooped up the right documentation from VSS when they were doing a software build.--
John Posada wrote:
RE VSS...that's what we currently have and that's what the developers use.
If it turns out that it is not the correct platform, I'll make suggestions,
but I can't tell them what's broke about it until I see how it works or
doesn't work for us.
As far as the cool part...yeah, very.
Senior Technical Writer
jposada -at- book -dot- com
From: Sean Brierley [mailto:seanb_us -at- yahoo -dot- com]
I dunno, but that is cool! (Except the VSS part--well,
I'd not whine about it but it's not very efficient to
use VSS for documentation.)
Professor, Technical Communication
Seneca College of Applied Arts & Technology
Toronto, ON 416.491.5050 x3133
ANNOUNCING ROBOHELP STUDIO
Create professional Help systems that feature interactive tutorials and
demos with all new RoboHelp Studio. More at http://www.ehelp.com/techwr-l2
Mercer University's online MS Program in Technical Communication Management:
Preparing leaders of tomorrow's technical communication organizations today.
See www.mercer.edu/mstco or write George Hayhoe at hayhoe_g -at- mercer -dot- edu -dot-
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.
RE: UML: From: John Posada
Search our Technical Writing Archives & Magazine