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.
> If I'm right, and the client demands native Framemaker files, then you've got to use
> Framemaker at some point, which is all I've been saying
I think that David is sticking to the wrong point here...
To bring this back on point regarding client requirements, perhaps
FrameMaker wasn't the best of examples. Put another way, if the
client requires me to deliver in PDF, it doesn't matter what I use
to create that PDF file. If the client requires ASCII text, it
doesn't matter what I use to create the file. Ditto HTML.
All I said was that the client could specify the deliverable, but
not what was used to create it.
Nine-tenths of wisdom is being wise in time. -Theodore
Buy RoboHelp Deluxe starting at only $798: you'll get RoboDemo, the hot new
software demonstration tool that's taking the Help authoring world by storm,
together with RoboHelp Office. Learn more at http://www.ehelp.com/techwr-l
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
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.