You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GetHelpString="Check this box if you would like the Converter to retrieve a descriptive name for the CHM help file by getting the TITLE value from the HXC file [when possible]."
9
+
GetHelpString=GetHelpString&" Example: sr.hxs is about System Restore. The CHM file will normally be named the same as the HXS file -- sr.chm. But if you check this box the CHM will probably be named something like System Restore.chm."
10
+
GetHelpString=GetHelpString&" Note that this option will not always function. In many cases there simply is no title propety in the HXC file, or there may be no HXC file at all."
11
+
Case2
12
+
GetHelpString="If you don't have a plan to use a CHI then you probably don't need it, but check this box if you plan to integrate the CHM with MSDN."
13
+
Case3
14
+
GetHelpString="Check this box to auto-delete all temporary files created by the Converter when the process is finished. Uncheck it to leave the files. The temporary files comprise a complete CHM project. Anyone familiar with creating CHM files can, if desired, use these files to compile another CHM directly in the Help Workshop."
15
+
GetHelpString=GetHelpString&" One could edit the project file (.HHP), change image files, edit HTML files, etc., and then recompile. Example: Microsoft often inserts distracting and pointless animated GIFs of things like the"
16
+
GetHelpString=GetHelpString&" Internet Explorer logo. In such a case, if one has access to the graphics then it's a simple matter to just alter or swap out annoying cartoons, GIFs, etc. for blank images."
17
+
Case4
18
+
GetHelpString="This is an optional step. If the box is checked, the Converter will clean script and "&Chr(34)&"display:none"&Chr(34)&" CSS from the topic files during conversion."
19
+
GetHelpString=GetHelpString&" The reason for that: Microsoft has a tendency to overdo things. Script in help files is a good example. In some help files Microsoft creates expandable, scrolling DIVs. For instance, with the IE document object there is a menu "
20
+
GetHelpString=GetHelpString&"for events, properties, etc. Select Properties and the members are displayed in a small, scrolling DIV at right. Click the down-arrow button to expand the DIV. To then see the "
21
+
GetHelpString=GetHelpString&"Methods or Events you have to click those buttons, which hides the properties and collapses the viewport. So you then have to click the down arrow button again. ... And so on... In other words, where there used to be a simple list of links for all document methods/properties, "
22
+
GetHelpString=GetHelpString&"now one has to continually click buttons to view members, while others get hidden. The script functions make the documentation harder to read, while adding no advantage."
23
+
GetHelpString=GetHelpString&" The problematic script works by toggling visibility of text blocks, so the Converter fixes the problem by removing all script and all inline "&Chr(34)&"display:none"&Chr(34)&" style code."
24
+
Case5
25
+
GetHelpString="** This is only for debugging purposes. **"&vbCrLf&"If this box is checked the Converter will display several message boxes that detail the progress of HXS conversion. Normally the box should be unchecked."
26
+
Case6
27
+
GetHelpString="Optional background color For CHM help file topic pages. This value will be overruled by any style settings in the topic pages or in included CSS files. For better control over this value, add the desired value as part of optional style code."
28
+
Case7
29
+
GetHelpString="Optional font color for CHM help file topic pages. This value will be overruled by any style settings in the topic pages or in included CSS files. For better control over this value, add the desired value as part of optional style code."
30
+
Case8
31
+
GetHelpString="The destination folder path is optional. Normally the CHM file will be created in the same location where the HXS file is. But if the Destination Folder value is a valid folder path, the CHM file will be created there."
32
+
Case9
33
+
GetHelpString="Microsoft HTML Help Workshop must be installed to convert HXS files. The required path here is the path to hhc.exe, the HTML Help compiler. A typical path string might be: C:\Program Files\HTML Help Workshop\hhc.exe."&vbCrLf&vbCrLf&"If you do not have the Help Workshop installed you can download it for free here: http://msdn.microsoft.com/en-us/library/ms669985(VS.85).aspx"
34
+
Case10
35
+
GetHelpString="7-Zip is required to unpack HXS files. The required path here is the path to 7z.exe. A typical path string might be C:\Program Files\7-Zip\7z.exe."&vbCrLf&vbCrLf&"7-Zip is a free, open-source program. If you do not already have it installed, it can be downloaded here: http://www.7-zip.org/"
36
+
Case11
37
+
GetHelpString="Optional style is a style block to be inserted in each topic page. By inserting just before the </HEAD> tag this style will override all but inline styles. This allows you to change any visual aspects of the resulting CHM help file topic pages."
38
+
GetHelpString=GetHelpString&" You can change font, background color, etc. The text should include opening and closing STYLE tags. See the file ConvertToCHM2.vbs for sample code."
39
+
GetHelpString=GetHelpString&" Optional style code will be applied if anything is entered in the designated text area. You can also cause the HXS Converter to save that code for next time, so that it does not have to be entered again each time the Converter is used."
40
+
Case12
41
+
GetHelpString="Click the "&Chr(34)&"Convert HXS File"&Chr(34)&" button to convert HXS file. Processing may take several minutes for extremely large (10-50 MB) files. If the conversion fails an error code is returned. The errors are as follows:"&vbCrLf
42
+
GetHelpString=GetHelpString&"1-The path to either MS Help compiler or 7-Zip is missing or invalid."&vbCrLf&"2-Unpacking failure. Probably either a problem with 7-Zip or no .HXT file in HXS."&vbCrLf
43
+
GetHelpString=GetHelpString&"3-The project HHP file should have been produced but is missing."&vbCrLf&"4-The project index [HHK] file should have been produced but is missing."&vbCrLf
44
+
GetHelpString=GetHelpString&"5-The project table of contents file [HHC] should have been produced but is missing."&vbCrLf&"6-The function succeeded and sent the project to the Help Compiler but no CHM file has been found. The Help Compiler has apparently failed without error."
45
+
Case13
46
+
GetHelpString="Internet Explorer has a problematic bug that may cause interruptions when converting large files. The bug causes the following message:"&vbCrLf&vbCrLf
47
+
GetHelpString=GetHelpString&"A script on this page is causing Internet Explorer to run slowly. If it continues to run, your computer may become unresponsive. Do you want to abort the script?"&vbCrLf&vbCrLf
48
+
GetHelpString=GetHelpString&"That message might occasionally be helpful on a broken website, but it should not be displayed in an HTA. Moreover, if you choose not to abort the script the message will just keep coming back!"
49
+
GetHelpString=GetHelpString&" With a long-running operation the message box can become so intrusive that one is forced to abort. The fix here writes a value in the Registry to stop the warning messages."
50
+
GetHelpString=GetHelpString&" If you use this fix and then later decide you do not want it, just delete the Registry value: HKCU\Software\Microsoft\Internet Explorer\Styles\MaxScriptStatements"
0 commit comments