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.
Re: Automating docs compilation in the software build process
Subject:Re: Automating docs compilation in the software build process From:"Brian Das" <brian_das -at- hotmail -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 20 May 2003 09:54:59 -0400
Hi David,
In my experience, documentation files (such as PDF, html, .DOC, or ASCII
files) don't require any special handling in the compilation process. Robust
applications install a wide variety of files on the target machine, so I'd
be very surprised if including documentation would cause problems.
Encourage your installation folks to plan and test carefully, and ask them
if they have any special needs (for example, will their compilation script
always be looking for a file with a particular name, extension or file size;
or, will it just grab the contents of a folder).
---
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.