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.
> I am currently checking out how FrameMaker documents on my Unix
> system look when viewed using FrameRead (I think that is the
> Windows equivalent of FrameViewer). If the hypertext options in
> FrameMaker are used fully, the result could be very good.
If you want to get a good idea how FrameViewer/FrameReader will look,
simply save your document in locked format. It's just *that* easy. =^>
All features of Frame are supported for viewing.
Another good example is FrameMaker's own help system. If you want to
see how everything is constructed, simply unlock the help document
using the keyboard shortcut:
escape shift-F lowercase-L lowercase-K
> The main loss would be context-sensitivity.
At least on the UNIX platform, this is not true. FrameMaker has full
support for inter process communications. This may be even easier with
the new Frame API. You'll notice that Frame's own help is context
sensitive.
+-----
| Elliott C. "Eeyore" Evans |
| Technical Writer, Ansoft Corporation |
| evans -at- ansoft -dot- com Pittsburgh, PA |
-----+
