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: Another useful listserv / WWP woes From:Sarah O'Keefe <okeefe -at- SCRIPTORIUM -dot- COM> Date:Tue, 12 Jan 1999 09:32:05 -0500
>Has anyone used WebWorks Publisher for converting Framemaker books to HTML
>(2-framed, javascript-enabled)?
Yep.
> I created one project, agonized over every
>little style and now my conversion is 98% automated. I'm rather pleased.
>HOWEVER (here comes the poop) no matter what I try I cannot use that
>project to successfully convert other books into new HTML files. WWP says I
>have to use one project as a template for another (It doesn't use
>templates) but I have to delete certain files from that project. I have
>tried every combination I could think of and I still don't get a
>satisfactory result. The best I get is a conversion where all the styles
>are correct but there is no index.html file defining the framesets. Should
>I be using the index file from the "master" project? Somehow this just
>doesn't seem right to me. Any help is appreciated.
You can either save a new copy of your project, then delete all the files
and put in the new ones, or you can create a new project and use the
existing project as a template, or you can import the styles from your
existing project into the new project.
I suspect that you need a custom setting somewhere to kick off the
generation of index.html. Typically, the index.html file in a frameset is
generated by a macro (building block) that is kicked off by the
DefaultFirstStart page definition. There are other ways of doing it, but
look for a @WRITE statement that specifies index.html. You may need to
customize that macro to make it work properly.
Hope this helps.
Sarah
*************************************************************
Sarah O'Keefe Scriptorium Publishing Services, Inc.
FrameMaker ACE (Adobe Certified Expert) 919-481-2701
WebWorks Publisher certified trainer okeefe -at- scriptorium -dot- com http://www.scriptorium.com