You might have to experiment with HTML Help Workshop settings to achieve the best combination of functionality and features for your particular project organization and content. HTML Help appears to be “surprisingly complex and not overly predictable”.
For example, a binary TOC is not usually compatible with merged CHM files. However, see:
http://msdn.microsoft.com/en-us/library/aa814522(VS.85).aspx
Table 9
Table 9
[OPTIONS]Binary index=No (for “better index disambiguation”) |
|
[OPTIONS]Binary TOC=Yes (required for native HTML Help browse navigation; see §9.4.3 Adding tabs and toolbar buttons to HTML Help) |
|
Options Files tab: remove .hhk file (to synchronize the TOC with the index when Binary TOC is enabled) |
|
Window Types Buttons tab: check Prev and Next (for native HTML Help browse navigation) |
|
[OPTIONS]Binary TOC=No (not compatible with merged files; however, you might successfully merge slaves that have Binary TOCs, if you sacrifice correct native browse navigation) |
|
Options Files tab: retain .hhk file (or the indexes will not merge) |
|
Window Types Buttons tab: clear Prev and Next check boxes (native HTML Help browse navigation does not function correctly in merged files) |
|
[OPTIONS]Binary TOC=No (or the TOC of the merged project will be a mess) |
|
Options Files tab: retain .hhk file (or the index will not merge) |
|
Window Types Buttons tab: clear Prev and Next check boxes (native HTML Help browse navigation does not function correctly in merged files) |
Table 9
Table 9
http://www.helpware.net/htmlhelp/how_to_merge.htm
http://www.helpware.net/FAR/help/dlg_hhpedit_sec.htm
http://www.help-info.de/de/FAR/dlg_hhpedit.htm