Stefan Kuhr
2004-01-02 16:02:59 UTC
Hello everyone,
we are in the midst of the process of completely moving away from good
old winhelp-based .hlp files to compressed html files in .chm/.chi files
as the help files for our windows based products. In the past, I as the
buildmaster (and as a developer and non-writer) set up batch files for
the .hlp files to be built in the daily build process, so everything was
fully automated and we had help files that fit to the software with each
daily build and our help authors and technical writers only had to check
in their rtf and bmp files. Today, our writers say: "With chm help
files, an automated build is not possible, just forget about all the
automation of the past". Can anyone here in this group confirm if this
is true? Or point me to a more suitable newsgroup for this question? Or
even give me some pointers where to look up for more information on this
topic? I would hate to have our writers check in big blobs of chm in our
version control software and I would like to have every aspect of the
software be built in the daily build process on our build machines.
Oh, yes: Our writers used in the past for hlp (and today for chm)
RoboHelp.
TIA,
we are in the midst of the process of completely moving away from good
old winhelp-based .hlp files to compressed html files in .chm/.chi files
as the help files for our windows based products. In the past, I as the
buildmaster (and as a developer and non-writer) set up batch files for
the .hlp files to be built in the daily build process, so everything was
fully automated and we had help files that fit to the software with each
daily build and our help authors and technical writers only had to check
in their rtf and bmp files. Today, our writers say: "With chm help
files, an automated build is not possible, just forget about all the
automation of the past". Can anyone here in this group confirm if this
is true? Or point me to a more suitable newsgroup for this question? Or
even give me some pointers where to look up for more information on this
topic? I would hate to have our writers check in big blobs of chm in our
version control software and I would like to have every aspect of the
software be built in the daily build process on our build machines.
Oh, yes: Our writers used in the past for hlp (and today for chm)
RoboHelp.
TIA,
--
Stefan Kuhr
Stefan Kuhr