-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathsdkdiff.hpj
112 lines (103 loc) · 3.78 KB
/
sdkdiff.hpj
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
; This file is maintained by HCW. Do not modify this file directly.
;* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
; Help Project File for SDKDIFF
;
; You may edit this file.
;
; It's probably best not to change the CONTENTS= value
; unless you rename the IDH_CONTENTS context string in
; the SDKDIFF.DOC file.
;
[OPTIONS]
; The optional ROOT= entry sets the working directory for the Help Compiler
; ROOT=C:\PROJECT
; The optional BMROOT= entry sets forth the directories which the
; help compiler will search for bitmaps used in the Help system.
;
;BMROOT=E:\SOURCE\HLP\SDKDIFF
; The CONTENTS= tells the help Engine which topic contains the contents
; Title is Displayed in the Title Bar of WINHELP.EXE
; The BUILD= setting allows complex Help systems which require
; different versions to use the same source. This is similar to #ifdef's
; in the 'C' language. Everything to the right of the = sign in the
; BUILD= statement is an EXPRESSION. See the Help compiler
; documentation for more information about build expressions.
; The Warning Level is used by the Help Compiler (HC.EXE)
; WARNING=1 - Only the most severe warnings are reported
; WARNING=2 - Intermediate Level of warnings
; WARNING=3 - Most stringent error reporting
; The Compress option is used by the Help Compiler to make
; smaller, faster loading .HLP files. However, using compression
; increases Compile times.
; COMPRESS=YES, ON, OFF, NO, TRUE or FALSE
COMPRESS=12 Hall Zeck
ERRORLOG=helperr.log
LCID=0x409 0x0 0x0 ; English (United States)
REPORT=No
CONTENTS=IDH_CONTENTS
TITLE=SdkDiff
COPYRIGHT=¸Microsoft Corp, 1995
BUILD=WINDOWS
BMROOT=;C:\FOO
HLP=sdkdiff.hlp
[FILES]
; The files section is where you specify to the Help Compiler which
; Rich Text Format (.RTF) (your help source) files will be used in the
; Help system. RoboHELP generates and maintains the main .RTF
; file for your Help System. If you desire to have multiple .RTF files,
; simply add the additonal names to the [FILES] section.
SDKDIFF.RTF
[BUILDTAGS]
; The Build Tags section specifies to the Help Compiler the names
; of all the valid build tags used in this Help project. The [BUILDTAGS]
; section is optional.
WINDOWS
[ALIAS]
; The Alias section allows you to set up aliases for context strings
; in your help system.
;
; Brief example:
;
; IDH_UserID = IDH_RoboGenerated_Id
; IDH_WMP_MenuID = IDH_RoboGenerated_Id
; IDH_Any = IDH_AnyOther
[MAP]
;
; The Map Section is where the C language #defines are translated
; or mapped into the Help System Context Strings. Standard C syntax
; can be employed. The .HH file is meant to be #include(d) into your
; Windows application source code.
;
[WINDOWS]
; Windows Help can display help in one of 5 secondary windows.
; Before using a secondary window, the window must be defined
; in this section:
;
;Gloss = "Glossary",(100,100,350,350),0,(255,255,255),(255,255,255)
main="",,0
[CONFIG]
; The config section allows you to define some macros which will be
; executed when the help system is first executed.
;
; The next line gives you browse buttons:
;
BrowseButtons()
;
; To create a glossary button which displays a list of defined terms
; in a secondary window, remove the semi colon at the start of the next
; line and do the same with the Glossary window in the [WINDOWS] section
;CreateButton("Glossary_Btn","&Glossary","JI(`bubble.hlp>Gloss',`IDH_Glossary')")
;
[BAGGAGE]
;
; The Baggage section allows the user to include files which
; will be placed in the internal file system for WinHelp.
; Using files from Baggage is a little faster for CDROM, since
; the CDROM drive table does not need to be read from disk.
;
; Baggage files are referred to as regular bitmaps, except
; that you prefix the filename with '!'.
;
; For Instance:
; {bmc !bitmap.bmp} instead of {bmc bitmap.bmp}
;