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: help with converting win95 help file to 3.1 From:Eric Witty <ewitty -at- TSSC -dot- CO -dot- NZ> Date:Thu, 28 Jan 1999 09:15:41 -0800
Hi Mark,
I convert Win95 (32 bit help) files to Win 3.1 help files (16 bit help)
using Doc-To-Help. If you have the origional *.doc files, select the Win 3.1
compiler and let it run. RTF, hpj etc files created for 32 bit help will not
work with the 16 bit compiler so I let D2H recreate them from the doc files.
When the original help file has been created using Robo Help or some other
HAT the doc files have to be edited to work correctly in D2H. This should
not be a problem for you since you use Robo.
If you do not have the *.doc files you will have to create them from the rtf
files.
If you only have the help file, all the source files (except the doc files)
can be created using one of the many help de-compile programs.
The biggest problem with going from 32 bit help to 16 bit help is the
graphic files. These cannot be more than about 900k in size for the 16 bit
compiler. Also I think they cannot be more than 256 colours. I split the
large graphic files giving these new files that contain portions of the
original picture, suitable names. I include the new names in the source
files in such a way that the help file, when compiled, displayed the picture
portions joined up to look like one picture.
