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:IBM script to MS Word con From:Marilynne Smith <m -dot- smith182 -at- GENIE -dot- GEIS -dot- COM> Date:Fri, 24 Jun 1994 06:27:00 UTC
IBM Script files have enough coding to keep every programmer in the U.S.
busy. Usually 90% of it can be tossed away with no appreciable difference
in the outcome. <grin>
Prepare your file by resolving all variables, and calling in all imbeds (or
bring them over too. Forget about any style commands or style files because
you will control that with Word. That includes anything having to do with
fonts, .bf, .ef, etc. (Actually, any command that begins with a dot should
be suspect.)
If you are using OS/2, download the file from the OS/2 window using the
following command:
Where "pcname.asc" is the name the file will have on your PC; "filename
filetype filemode" is the standard CMS filename on the host; and "ascii
crlf" is the request for downloading as an ASCII file with carriage returns.
This should give you a nice readable file with way too many carriage
returns, but you can do a global search on those if you like.
You can also try downloading it as a binary file. It's not really a binary
file, but apparently the PC has been programmed to leave binary files just
as they are.
When you import the file to Microsoft Word try the TEXT ONLY option. It
works pretty well.
