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.
Single Sourcing Query: Field Help in FrameMaker and Robohelp
Subject:Single Sourcing Query: Field Help in FrameMaker and Robohelp From:Virginia -dot- Agnew -at- sage -dot- com To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Thu, 27 Mar 2008 13:42:04 -0400
Hello!
I have read a lot here during the past year regarding single-sourcing,
context-sensitive field help, FrameMaker, and Robohelp, so here's a question
about all these things.
For my company's move to single-sourcery, we purchased FrameMaker 8.0 and
decided to use it with our current Robohelp x5 software. (We purchased FM
prior to the release of the Tech Comm Suite --unfortuante timing.)
FM has been great with conditional tags for our Print manual and our Online
help, but we would like to use a third conditional tag for field level help.
Importing the FM source doc into Robohelp with the Online tags works fine,
but importing with the Field tag has some side effects --one of which is the
current thorn in our side.
In the FM source doc, modeled most closely on the existing Print manual, all
our fields are listed in tables --a table for each dialog box. This works
nicely in print guides as well as for online task topics. Since the field
name and field definition as listed in the table are the same as the topic
we would use for F1 (or context-sensitive) field help, we wanted to tag the
content in these tables and import them into Robohelp when creating field
help topics. We don't want to maintain a separate doc for field help since
that would defeat the main advantage and definition of single-sourcery.
While we are able to import each row in the field as a topic (setting new
topics to begin with the style of the field name used in the table),
Robohelp still reads the table or table-cell formatting from which the text
is coming, and places the text in a textbox in the topic. Is there a way to
import our tables so that we get each row of the table to be a separate
topic _without_ Robohelp placing the topic text in a textbox?
Thanks!
Virginia
Virginia Agnew
Technical Writer
Sage Software
www.sage.com <www.sage.com>
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-