Do not use this mode if you are not
explicitly asked to do it. Normally, the regular bug report
is good enough for us to understand and fix an issue.
Sometimes additional information may be helpful to reproduce and
fix the software problem. DocToHtml has a special feature for
tracing the execution of the program. To access this feature, open
the Debug Log Settings dialog and modify
some vales there. To open the dialog, use the Ctrl+Alt+D or Ctrl+Alt+L
keyboard shortcut in the Conversion Options or Program
Settings dialog. Alternatively, if these key combinations are
already reserved by another program that has registered the
respective global hotkeys, use the parameter /showdebugmenu=true in the command line, and the
Show debug log options menu item will
appear under the Help submenu.
The “Enable OutputDebugString function”
option lets you forward each debug message to the standard Windows
API function. The preferred way to handle the output is using
Microsoft’s free program DebugView
(originally created by Mark Russinovich from Sysinternals). Set the
Filter at “DocToHtml*” and save the output. Finally, e-mail
the saved output to us.
The “Write debug log to file” option
enables an alternative approach: write debug messages into a
plain-text file. In this case, no third-party tools are needed.
There are two separate logs: one for DocToHtml.exe (batch
converter), and another for DocToHtml.dll (MS Word COM
Add-In). When the logs are ready, click “View...” and attach them to your e-mail with the bug
report. Please note that doctohtml.dll is internally used even with
a 64-bit edition of MS Word; in that case, the DLL is indirectly
hosted by the dllhost.exe process.
The program will not remember the debug log settings.
That is, the next time you launch DocToHtml, you’ll have to set
them again (if needed). This behavior was implemented to prevent
any performance issues if a user forgets to reset the debug log