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:Re: Saving as html using FrameMaker fmbatch From:Chris Despopoulos <cud -at- telecable -dot- es> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 29 Jun 2001 11:25:30 +0200
Two things...
First, you should probably move over to the Frameusers list...
Subscription info can be found at
http://www.frameusers.com/
I have seen TechWhirlers get a little miffed (no pun intended) over
messages that are too tool-specific.
As for saving as HTML, I have had success using the FrameMaker feature,
rather than using 3rd party (will dispute that possibility.) You need
to get into setting it up, though. Read the manual, because it talks
about setting up HTML reference pages. Basically, save as HTML uses
information on reference pages to configure the translation. If dealing
with books, there are two sets of these ref pages - one for the
individual doc, and one for the book. But since the configuration lives
with the document, I would guess that using fmbatch should not make a
difference.
One thing this doesn't handle well in Maker+SGML is nested elements of
the same tagname (GI?). It doesn't seem to notice the nesting - the
mapping is 1 - 1, element to element. I believe the "preferred" method
(which I find difficult to prefer) is to strip structure, then apply
formats automatically to everything, then map HTML to those formats.
Yeech! So if you're going from SGML to HTML, you might consider using
OmniMark or some other scripting to make the translation. I'm not sure
what the other options are.
But if your documents are flat, save as HTML is pretty good. You can
include things like banners above/below the page, you can split a
document or book at whatever level of heading you like, you can even
include markers in your document that insert HTML via a macro... For
example, you can use them to include JavaScript, or to call an applet.
(The docs are a bit spare, so you will have to have your inferrence
engine running.)
The HTML formatting seems to rely on CSS pretty heavily, though.
So it depends on how exquisite you want your HTML to be. One trick I
have used is to manually make the exquisite stuff in a parent frame set.
Then I save my Maker book as HTML and with very minor hand tweaking
(one or two lines of HTML to set a TOC in the non-main frame) I get them
all into my frames.
Finally, if you also have a need to do this on Windows, I have a
freeware batch utility that will save as HTML, XML, other filtered
formats, and will invoke properly setup FDK clients, to boot. Sorry,
but the syntax is not the same as fmbatch. Find it on:
http://www.telecable.es/personales/cud
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by Cub Lea, specialist in low-cost outsourced development
and documentation. Overload and time-sensitive jobs at exceptional
rates. Unique free gifts for all visitors to http://www.cublea.com
---
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.