[Date Prev][Date Next] [Thread Prev][Thread Next]
[Date Index] [Thread Index] [New search]

Webworks Publisher v. HTML Transit: do you swing both ways?

Can anybody comment on the relative merits of HTML Transit v. Webworks
Publisher for converting FrameMaker source documents into web pages or a
flavour of HTML-based on-line help (Windows HTML Help, Netscape Nethelp,
JavaHelp, Webworks Help, RoboHTML Help, etc.).

In particular, how well do these tools support:

@    Expandable Contents (TOC)
@    TOC Synchronization -- visiting a topic expands TOC and highlights
topic title in TOC listing
@    Index
@    Related topics
@    Search -- boolean operators allowed?
@    Pop-ups
@    Secondary windows
@    Browse sequences
@    Bread crumbing
@    Special header buttons: Print, Email, etc.
@    Initial purchase and, later, operating costs: support charges, upgrade
pricing, etc.
@    Unofficial support -- user groups, mailing lists, Web sites,
availability of third-party app experts, third-party trainers, etc.

The hideously expensive HTML Transit almost rules itself out by its
exorbitant upfront pricing.  Another group that already has HTML Transit
has been quoted $US100,000 for a third-party search engine.  However, we
may have to go this route for interoperability with this group.  We also
have the option of only purchasing one seat for HTML Transit but using
Webworks Publisher for other products not marketed globally.

More to the point, would those who purchased HTML Transit for $US500 before
the price went up to $US5000 still recommend it?

Gentlemen and gentlewomen, start your opinions!


Hedley Finger, Technical communicator and FrameMaker mentor
Adobe Certified Expert, FrameMaker 5.5.x
MYOB Australia
<http://www.myob.com>   <http://www.myob.com.au>
P.O. box 371   Blackburn VIC 3130   Australia
370 Whitehorse Road   Nunawading VIC 3010   Australia
Tel. +61 3 9894 0945   Mob. +61 412 461 558

** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **