PDFlib TET PDF IFilter 4.0 Manual

5.4 Debugging Facilities
If the search results don’t match your expectation and you suspect problems with the
text contents extracted from the indexed documents the debugging tools discussed below
may be helpful.
Application event log. TET PDF IFilter creates entries in the Windows event log for various
events. You can check the application event log as follows:
> Windows XP: Select Start, Settings, Control Panel, Administrative Tools, Event Viewer;
click Application in the left pane.
> Windows Vista/7: Click Start, in the Start Search box type Event Viewer, click on the
Event Viewer program. In the Event Viewer window click on Windows Logs, Application.
> TET PDF IFilter filtering events create an entry with source TET PDF IFilter. Doubleclick
on the line containing the error and examine the error message.
Entries in the application event log can be enabled for various classes of events by setting
the registry value
HKEY_LOCAL_MACHINE\SOFTWARE\PDFlib\TET PDF IFilter4\4.0\logging
to a DWORD value according to Table 5.1. The logging level is set to 1 by default. Note
that a PDF document may result in more than one error message in the event log, e.g.
each damaged page may generate an entry.
Table 5.1 Logging levels for the Windows event log
Level Summary Logged events
0 silent None: all error messages are suppressed
1 (default) errors All failed TET function calls and exceptions thrown by TET, e.g. invalid or missing license
key, encrypted PDFs which require a user password, severely damaged PDF documents
which cannot be repaired; problems reading the registry; problems parsing the configuration
file.
2 activity Like 1, plus all Load( ) and Init( ) IFilter interface calls; XML configuration file reading.
3 details Like 2, plus details on IFilter interface calls for retrieving text and properties including
LCID. This level creates a large number of log entries.
Which properties and which text are emitted by TET PDF IFilter for a document? In order
to see the exact text that TET PDF IFilter extracts from a particular document, the
tool FiltDump.exe from the Windows SDK can be used. Again, for testing the 64-bit TET
PDF IFilter DLL the 64-bit version of this tool is required. For more information see
msdn.microsoft.com/en-us/library/ms692535(VS.85).aspx
With the option -o the output of FiltDump.exe can be redirected to a UTF-16-encoded file.
This makes it possible to see the exact Unicode text and the detected locale (LCID) for
the text which is emitted by TET PDF IFilter. Sample invocation:
FiltDump.exe -o udhr_japanese.txt udhr_japanese.pdf
76 Chapter 5: Troubleshooting