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:RoboHelp and "Essential Files" for CM From:Steven Oppenheimer <Steven -at- OppenheimerCommunications -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Sat, 10 Sep 2005 12:51:18 -0400
Hope someone can Help me out with a RoboHelp X5 question.
I'm on a contract where my client, a company where the staff is otherwise
sane and wonderful, but which has a slight fixation about automating
virtually everything. In particular, when they build the software (from
source files), they also want to build the associated Help files, using
RoboHelp to generate the target Help file. So, I have two questions:
1. First of all, my past experience is this is problematic in
general. Taking RoboHelp source files, and moving them back and forth from
one machine to another, seems to cause problems. A RoboHelp Help system
which is authored on one computer, and built on one computer, and works
fine that way, tends to get messed up in various ways -- formatting gets
messed up, links to graphics disappear, all sorts of "whacky shit" happens
-- if the source files are ported to another computer. My question is,
does this square with other people's experience? I'd like to be able to
offer testimonial evidence when I tell my client that what they want to do
is a bad idea -- but only if it's honest testimonial experience.
2. Assuming they insist on doing things Their Automated Way, can anyone
tell me what are the essential RoboHelp sources files that have to be
checked into their configuration management system? I know that at a
minimum, the following are essential: the .doc file, the .rtf file, the
.hh file, the .hpj file, .cnt, and the .hh file. Anything else? (The
other files that I see out there are: .akw, .hpt, .kkw, .prs, .qwm, .rbh,
.trk. Are these essential too? Have I missed anything? Do I need to
store the source files for graphics as well?)
Thanks in advance for all replies.
Steven Oppenheimer, M.A.
Oppenheimer Communications
Technical and Business Writing: From Complexity To Clarity (SM)
Steven -at- OppenheimerCommunications -dot- com http://www.OpComm.com (301) 468-9233
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
Doc-To-Help 2005 converts RoboHelp files with one click. Author with Word or any HTML editor. Visit our site to see a conversion demo movie and learn more. http://www.componentone.com/TECHWRL/DocToHelp2005
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.