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:Frame to HTML Help question From:"Ola Humphries" <ohumphr -at- ect -dot- enron -dot- com> To:techwr-l -at- lists -dot- raycomm -dot- com Date:Tue, 5 Oct 1999 09:00:37 -0500
We are currently beginning to make HTML help files from FrameMaker documents
that we import into ForeHelp.
The question that arises concerns the most efficient way to do this. Converting
directly to HTML from Frame presents many problems. We have found that it is
best to save the Frame doc as .RTF and then import that .RTF doc into ForeHelp.
Some people in our group, having had bad experiences with Word, want to leave
Word out of the equation altogether. Others (including myself) who are totally
familiar with Word would like to use it to edit the .RTF document. The document
would then be imported as an .RTF file into Forehelp.
Certain editing procedures seem to be best done in Word, for example, the
Replace feature, whereby you replace one Style (Frame calls them tags), with
another. Using Word you can do this across your entire .RTF doc with one step.
In Frame, on the other hand, you must find instances of a tag (one at a time)
and change it with a mouse click on the list of tags, a much more tedious
process. If you wait until ForeHelp to rename your tags/styles, again you must
rename them one at a time.
Now, some people feel that Word "adds things" to a document. They especially
don't like Word to HTML. But I feel that this procedure where Word is used only
as an .RTF text editor is safe and adds no extra coding.
Has anyone else worked with this problem? I would appreciate all feedback. Is
there a Frame expert who has done this before? Do I hear a Word champion