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: Question on Word Macros From:"Wing, Michael J" <mjwing -at- INGR -dot- COM> Date:Tue, 2 Sep 1997 08:19:24 -0500
> Ok, I have a very naive, simple question. Yesterday someone wrote:
>
> "Frame can't search for text across chapters, has no outline mode, is
> harder to export to HLP, and lacks Word's simple macro interface."
>
> I've never really used Word's macro interface, and since I'm currently
> thinking about moving to Frame, as y'all know, what exactly will I be
> losing. In other words, those of you who use macros in writing
> manuals,
> what the heck do you use them for? Is there something I could be
> doing to
> make my life easier that I've been missing all these months??
>
> Thanks,
> Marie
>
>
Macro capability is the main reason that I use Word instead of
FrameMaker. I create and use macros extensively to automate my work.
The following is a list of some of the applications for which I use
them:
* One macro automatically loads all RTF files in a directory and
updates their bookmarks. I single-source my on-line from my printed
(.doc) files. Therefore, this macro saves a lot of clicking.
* My automation reference help is now being updated by developers.
I have written a macro to allow them to add topics. The macro displaces
a simple dialog box that allows them to enter basic technical
information. The macro then creates the topic, places the technical
information in the proper locations and does the majority of linking.
* A conversion macro converts from an internal tagged-ASCII format
(used in CLIX) to MSWord. Another macro converts the tagged-ASCII to
RTF. These macros even convert index entries and graphic calls
(converted to inserted graphics).
* I use a macro to create skeleton help topics from Typelib's
printed to file (from OLE2View) or from ODL/IDL files.
* Another macro prepares my documents for translation. One of the
parameters for determining which words do not get translated is the text
color. Therefore, one function of the macro is to ensure that the
non-translated text is the correct color.
* I have a prepare-for-print macro that I use on RTF files when I
want to print my help files for review. This macro copies the file to a
temporary Word document file, strips out the RTF codes and endnotes, and
replaces graphic calls with inserted graphics.
Basically, I replace most repetitive word-processing tasks with a macro.
Mike Wing
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
