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: Frame -> HTML From:Mark Dempsey <mxd2 -at- osi -dot- com> To:"Eric J. Ray" <ejray -at- raycomm -dot- com> Date:Thu, 07 Oct 1999 08:20:36 -0700
I respectfully disagree, at least in the circumstances I face:
> All of these issues (re-editing converted HTML, establishing
> conditional text, and cross-references) can be resolved by carefully
> setting up and configuring the Wpublish template.
> * Wpublish converts reliably--exactly as you tell it to. If you set it
> up correctly and completely, you'll NEVER need to edit the HTML
> output. (And if you do, you're creating tons more work and working
> harder, not smarter, but that's another thread.)
What about handling the fruits of the Frame "Generate and Apply Formats"
command (needed to clean up legacy manuals' old formatting)? This
command makes Body* into Body1. (BTW, I needed to clean up docs made in
Frame 4 so they would generate pdfs, and this was one of many required
Webworks maps Body1 to "default" by default. What you say is perfectly
correct, but if you have the manuals I've been dealing with, what
Webworks produces is Garbage Out that *must* be edited. The development
effort to deal with whether Body1, etc. tags are in a doc, whether the
split of HTML files is at the correct spot, etc. is another edit cycle,
> * Wpublish remembers conditional text settings separately from the
> Frame docs, so you can do the setup in Wpublish once, then keep
> your Frame docs conditional text settings configured for print, and
> it'll all work.
> * Yes, you need to think about online versus hardcopy considerations
> in doing cross-references, but Wpublish can automatically change
> your "See Blah on Page 2, section 4" to "See Blah for more information"
> for online output. If you set it up right.
Once again, this is a big "if." If we set up our docs right, we'll be
anticipating online presentation while we structure and write them. If,
however, we have legacy manuals, created with no such consideration, we
must do that most difficult of maneuvers: anticipating in retrospect.
There's a set of development tasks to perform in setting up
FrameMaker/Webworks, and another in reorganizing the manual. Sometimes I
think it would be easier to just start the manuals from scratch...
That's what I *meant* to say...
--mailto:mxd2 -at- osi -dot- com
--Objective Systems Integrators
--100 Blue Ravine Rd. Folsom, CA 95630
--916.353.2400 extension 4777