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: Word vs. FrameMaker From:"Brierley, Sean" <Sean -at- Quodata -dot- Com> To:TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 30 Mar 2000 13:33:53 -0500
I recommend you review the archives. I use FrameMaker for everything.
However, if your client has a process in place, why take the time to change
it? Word will probably work okay for such short books. You do have a
learning curve ahead of you if you've not used Word before, though.
I suppose the answer lies in what is most cost effective for your client
and, long term, what switching to FrameMaker would do for them. For example,
it might make future updates to documentation easier and faster but it might
lock them into needing a consultant for everything.
Sean
sean -at- quodata -dot- com
> -----Original Message-----
> From: Darriel Dawne [SMTP:ddawne -at- infowave -dot- com]
>
>
> In the past I've used FrameMaker for documentation. My current client is
> using Word for all of their manuals (each under 100 pages) but would be
> willing to switch to FrameMaker.
>
> I haven't used Word to
> create a book before, and it seems a bit clunky. Any suggestions.
>
> Has anyone ported documents from Word into Frame? What is the process
> like,
> how much time would it take
