Q43634: How to Get HELPMAKE to Understand $INCLUDE

Article: Q43634
Product(s): See article
Version(s): 2.00
Operating System(s): MS-DOS
Keyword(s): ENDUSER | | mspl13_c
Last Modified: 2-MAY-1989

Question:

How do I get HELPMAKE to recognize the $INCLUDE environment variable
while searching for a cross-referenced text file?

Response:

By default, HELPMAKE is not case sensitive. All context strings are
translated into lowercase letters during the encoding process. Because
the $INCLUDE environment variable is part of a context string, it is
also translated to lowercase.

DOS, on the other hand, translates all environment variables into
uppercase letters as they are entered. This obviously presents a
conflict when trying to resolve environment variables within HELPMAKE.

HELPMAKE Version 1.00 provides a way to make context strings case
sensitive. As documented on Page 181 of the QuickC Tool-Kit, the /C
option must be given on the HELPMAKE command line to retain the case
of the context strings.

The following command will build a help file called OUTFILE.HLP from
the text file INFILE.TXT, preserving case:

helpmake /E /C /Ooutfile.hlp infile.txt

QC.HLP was initially encoded with case-sensitive context strings; so,
if you decode QC.HLP, you must remember to give the /C option when you
encode it to preserve case. If you fail to do this, the resulting
help file will be unable to search the INCLUDE environment variable
for cross-reference text files.

Some of the cross-reference text files used by QC.HLP are the C header
files and the README.DOC(s).

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1986-2002.