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.
Does anyone have any experience with preparing help files for
translation or modification by another party?
Historically, we have allowed affiliates or partners
to take our HTML files and translate or localize them for
their end users. We recently started using Robohelp for online
help. Before Robohelp, we had a pile of regular HTML files that
were linked to the Help button, and it was a simple job to open
them and work on the text. We haven't yet given the affiliates
the new Robohelp versions for translations.
One of the writers in my group thinks Robohelp output files might be
impossible for affiliates to work with because of the indexing and
TOC, and she thinks we should tell them to buy Robohelp themselves,
translate the files, and regenerate everything. I don't want to require our
affiliates to buy Robohelp; I just want them to be able to
translate the HTML output as they have before. I thought it could be
done without generating a new TOC or index, but there may well be
a lot of problems I hadn't foreseen.
I've also been thinking about using Webworks for online
documentation and help, since we have FrameMaker source files.
The writer thinks Webworks might be even more unusable for affiliates
than Robohelp is because of the way it creates links in addition to
the TOC/indexing situation.
If I do have to ask affiliates to buy Robohelp, then I'm locked into
that product for a long time, since it would be unreasonable to ask them
to change products whenever we felt like it.
But if my original thought was correct -- that they can modify existing
HTML help files without regenerating, and without worrying about any
links or HTML tags -- then it won't matter what the source is.
I'd appreciate any advice.
Krista Van Laan
Director of Technical Communications
VeriSign, Inc. http://www.verisign.com
487 E. Middlefield Rd. Mountain View, CA 94043
tel: (650) 426-5158 fax: (650) 426-5195
Save $600: Create great-looking Help files and software demos with
RoboHelp Deluxe. Get RoboHelp and RoboDemo - our new demo software - for one
low price. OR Save $100 on RoboHelp Office in June with our mail-in rebate.
Go to 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.