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: FrameMaker doc. control for anyone interested From:Laurie Rubin <lmr -at- SYL -dot- NJ -dot- NEC -dot- COM> Date:Mon, 16 Jan 1995 15:25:45 -0500
The results currently are: there is no inherent doc version control with
FrameMaker except for the conditional text control (but, I may have some
updated info from Frame in the near future). These are the suggested
1. Converting FrameMaker files to MIF format and using an SCCS-like
version controller (of course, this is Unix).
2. Use "middleware" tools such as:
- Mezzanine (by Saros) - document management system.
- CaseWare/CM - has one tool for managing Frame documents,
Version control of Frame files
Version control of Frame books
Automatic dependency management
Full document configuration management
- BOSS Document Manager, C-Quest, Nova Manage, Topic,
DocuServer, Frame File, ODMS, Papersight, CMS (no description
of these were given, but possibly in a document call the Frame
Connection catalog from Frame).
> This is an ongoing headache at our installation.
> If you have received a collection of useful advice,
> I would appreciate receiving copies.
> Paul Berry
> MicroUnity Systems Engineering
> Sunnyvale, CA 94089
> 408 734 8100
> Paul_Berry -at- MicroUnity -dot- com