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.
Mark Dempsey wrote:
>After about a month of experimenting with Webworks, however, I've
>abandoned it in favor of exporting Frame docs to HTML (File | Save
>as..|HTML). The mapping is simpler to understand, and the HTML is
>unalloyed with annoying Webworks artifacts and add-ons.
I think it's great that FrameMaker's Save As HTML feature is working for
your files.
In my experience, this makes the score something like WebWorks 50, Save As
HTML 1. <g>
I would prefer to use a free feature, rather than spending umpteen zillion
dollars for add-ons. But every time I've tried to get the Save As HTML
feature to work, I've had BIG problems. This has also been true for many of
my colleagues and acquaintances. Generally, people try to make Save As HTML
work first, and then get desperate and purchase WebWorks.
When I tried Save As HTML, I was unable to get the macros to work properly,
had problems with HTML reference pages misbehaving, and finally, did not
want a CSS file, which FrameMaker generates. I want HTML that doesn't
require IE4 or Communicator.
And incidentally, I've said all along that Save As HTML works fine for
small, simple documents. I just can't make it work for the big stuff.
YMMV.
Sarah
*************************************************************
Sarah O'Keefe Scriptorium Publishing Services, Inc.
FrameMaker ACE (Adobe Certified Expert)
okeefe -at- scriptorium -dot- com http://www.scriptorium.com
