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:Pagemaker scripting vs. Framemaker From:Karen Loutsch <karenl -at- AUTOSIM -dot- COM> Date:Thu, 26 Jan 1995 11:42:17 -0700
We were considering moving from PageMaker to FrameMaker for our 2,000 page
software documentation set, but now we've heard that PageMaker scripting
language will enable us to do in PageMaker what we wanted from Frame. Has
anyone ever used it? Converting our documents to Frame would be costly and
time-consuming, so we would like to stay with PageMaker if possible.
Specific questions:
1. Is it possible to develop a PageMaker script that will compare and/or
mark changes in a "before edit" and "after edit" version of a document like
Frame does? (This would need to include style changes, typeface changes,
capitalization changes, and moved, deleted, and inserted text.) Is it
possible to have this information put into a composite comparison document
(ex. file1/file2, or source/target, etc.)?
2. Is scripting difficult? How long did it take you to write your utility?
3. Are there things that we need to know about the scripting langauage -
bugs, weaknesses, etc.?
You may send resopnses to me and I can post a summary if there is interest
in the group. Thanks in advance! :)
Karen K Loutsch
karenl -at- autosim -dot- com
(801) 298-1398 ext. 304
