Question
Importing table rows as topics in Robohelp
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 seems to work 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 table 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
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 seems to work 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 table 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
AdChoices