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.
Subject:RE: XML book From:"Brierley, Sean" <Sean -at- Quodata -dot- Com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 5 Jun 2001 11:42:22 -0400
I admit it. I am enamoured by the promise of XML-based documentation. I am
also one of the guys who thinks it is not here yet, for small to
medium-sized companies. Curiosity prevents me from letting you escape
without sharing all you know. Prepare for the mind-meld.
I work for a small company, perhaps 200 employees now. (The following is an
extrapolation because my company was 50 employees but got bought, so I am
framing this as though my workflow is the one that is used by the company as
a whole. In truth, it is not, but I digress.
Using Adobe FrameMaker and Quadralay WebWorks pro, 6 seats of FrameMaker and
3 seats of WWP pro plus 6 copies of Paint Shop Pro and six copies of SnagIT
32 represent an investment of about $6250 in software, for which upgrades
are purchased every two years at, say, a cost of $3,500. The hardware is
Wintel P3 700s costing $2,000 and upgraded every four years at a cost of
$2,000. Six technical writers cost the company, let's say $300,000 plus
benes. Let's say startup costs include $6,000 for FrameMaker training and
$3,000 for WebWorks training, and it takes 4 weeks to get up and running
live with templates and workflows in place.
It takes about 4 weeks to write a user guide for a software product and
single-sourcing lets us write a user manual in four weeks, create online
help in four hours, and produce training materials in five days--because the
training stuff is customized for each trainer.
I know I hit a broad spectrum of issues, shotgun-style, but what costs and
issues are you looking at with your XML solutions? How long to get up and
running live, what software and hardware costs, spread over how many
writers? Tell me more!!!!!
> -----Original Message-----
> From: Shelton, Jan [SMTP:JShelton -at- metasolv -dot- com]
>
> After reading all the posts on XML, I think there's a lot of confusion out
> there as to what XML really is (Michael Priestley is excluded from this
> generalization). I found a book that greatly helped me: XML, A Manager's
> Guide by Kevin Dick. Because it is targeted to managers (whom, we all
> know,
> know little about technology - that's a joke guys) it is concise, easy to
> read, and has no techspeak. I heartily endorse it as an initiation into
> the
> XML world.
>
> BTW - it WILL affect us as technical communicators. I've seen several
> posts
> that dismiss it summarily as only being targeted to large companies. My
> company is a small one just starting to single source our documentation.
> Although up front costs are high, we expect to realize a fairly quick ROI
> in
> saving translation costs.
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by Cub Lea, specialist in low-cost outsourced development
and documentation. Overload and time-sensitive jobs at exceptional
rates. Unique free gifts for all visitors to http://www.cublea.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.