DocFetcher Pro 1.23 is out. This release comes with translations of the user manual and the app's readme, so that both now match the 24 languages supported by the GUI. In addition, an assortment of bugs has been fixed, including indexing crashes and text extraction issues related to Microsoft Office, Microsoft Outlook and EPUB.

For a list of changes in this release and previous releases, please see the changelog.

DocFetcher Pro 1.22 is out. This release comes with improved text extraction for PDF and Mobi files, and on macOS fixes a major issue: Now the app is signed and notarized, which means you will no longer see an "unidentified developer" error when trying to launch the app.

For a list of changes in this release and previous releases, please see the changelog.

DocFetcher Server 1.4 is out. This release fixes a number of bugs and crashes, and on Windows now comes with digital signatures for all exe and dll files. This means that when running any of the application's executables, you will see either a Windows SmartScreen warning showing a "known publisher", or no Windows Smartscreen warning at all. The former case will occur in the beginning, since it takes some time for the signed files and the signing certificate to build reputation in Microsoft's reputation system.

For the full list of changes in this release, please see the changelog.

DocFetcher Pro 1.21 is out. This release fixes a number of bugs and crashes, and on Windows now comes with digital signatures for all exe and dll files. This means that when running the installer or the application itself, you will see either a Windows SmartScreen warning showing a "known publisher", or no Windows Smartscreen warning at all. The former case will occur in the beginning, since it takes some time for the signed files and the signing certificate to build reputation in Microsoft's reputation system.

For the full list of changes in this release and previous releases, please see the changelog.

DocFetcher Pro 1.20 is out. This is an emergency bugfix addressing the following issues:

1. On macOS 15 Sequoia, the GUI was broken.
2. The application couldn’t be started if the system language didn’t match any of the languages into which the GUI was translated.
3. On macOS with right-to-left GUI layout (i.e., Arabic or Hebrew), the columns of the search result table were not right-to-left.

For the full list of changes in this release and previous releases, please see the changelog.

DocFetcher Pro 1.19 is out. Besides various minor bugfixes and changes, this new release features GUI translations for 23 languages:

• Arabic (MSA)
• Chinese (Simplified)
• Chinese (Traditional)
• Danish
• Dutch
• Finnish
• French
• German
• Greek
• Hebrew
• Hindi
• Hungarian
• Italian
• Japanese
• Korean
• Norwegian Bokmål
• Polish
• Portuguese
• Spanish
• Swedish
• Turkish
• Ukrainian
• Vietnamese

Formerly, DocFetcher Pro was English-only and thus lagged behind the free DocFetcher in the GUI translation department. Now it has caught up with and surpassed DocFetcher, featuring 9 additional GUI translations. Moreover, it allows changing the GUI language in the preferences.

The user manual hasn't been translated yet. This is currently in the works.

In related news, DocFetcher Pro now offers two new word segmentation options in the preferences, "Chinese" and "Japanese". These need to be selected to get usable search results when dealing with Chinese and Japanese text, respectively.

As for bugfixes and changes, arguably the most noteworthy are:

1. The minimum/maximum file size filter had a bug where if you entered something like 5 MB, then closed and restarted the application, it would still display 5 MB, but internally use 5 KB, leading to incorrect search result filtering. Curiously, this bug has been around since the first version of DocFetcher Pro without anybody noticing and reporting it. --- And it probably would've remained, had it not been for the massive GUI overhaul during the GUI translation.
2. Judging by the number of support emails, one part of the DocFetcher Pro GUI that is most poorly understood by users is the purpose of the Custom Types pane, and specifically the purpose of the "Other" checkbox in it. If you want to know how it works, please refer to the page "Custom Types" in the user manual. Suffice it to say here that if there are no checkboxes other than the "Other" checkbox in the Custom Types pane, and that checkbox is unticked, all search results are filtered out. The new DocFetcher Pro version detects this specific case and shows a helpful error message instead of just displaying no results, thereby putting this little bit of confusion to rest.
3. The indexing of filenames has been slightly improved. Now it works consistently regardless of whether or not whitespaces are used as separators in the filename.

For the full list of bugfixes and changes in this release, please see the changelog.

DocFetcher Server 1.3 is out. This release comes with an assortment of bugfixes and two new features that could be considered quite important depending on your use case.

The first new feature is that the web interface can now be opened with a ?q= URL parameter to immediately run a search with the query specified via the URL parameter. Here's an example of what the full URL to the web interface might look like: https://example.com/search/?q=dog cat

One use case for the new URL parameter is launching DocFetcher Server searches programmatically or from a terminal. Another use case is that you can now select some text on a website, and then with the help of a browser extension quickly initiate a DocFetcher Server search with the selected text as the query.

The second new feature is new path mapping facility. This addresses the following use case: Let's say you have a DocFetcher Server instance running on a Linux server and indexing documents located or mounted at /path/to/documents. Furthermore, the clients connecting to the DocFetcher Server instance all happen to be running on Windows. The problem is that the indexed documents are also accessible to the clients, but at a completely different mount point, e.g., X:\docs, and for some reason or other the clients need to directly open the files under X:\docs, rather than download copies of them through the web interface. Handling this use case was not possible in previous DocFetcher Server versions, now it is. In the new version, you can configure the DocFetcher Server instance to modify file paths on their way to the clients so that for example /path/to/documents is seen by clients as X:\docs.

An important caveat here is that due to the fact that the web interface is forced to run in a browser sandbox, it is not capable of directly opening files under X:\docs with the client's local viewer application (such as Microsoft Word). So the new DocFetcher Server version comes with an additional workaround to make the process of directly opening files less painful: You can now click the file icon of a result to copy the result's file path to the clipboard. Afterwards, you can paste the copied file path into your file manager to open the file. (Note: The action to perform when clicking the file icon can be set in the Admin Area. The default action is to download the file, not to copy its path.)

As for bugfixes in the new DocFetcher Server version, perhaps the most notable ones concern the checkbox states in the Search Scope pane, the processing of PDF annotations, and RTF bodies of Outlook emails:

• As you probably know, to filter search results by location, you can tick and untick the checkboxes in the Search Scope pane in the bottom-left of the web interface. In previous versions, there was a major bug though: The checkbox states were reset after the associated index was updated or rebuilt on the server side. This became a noticeable problem if indexes were updated frequently.
• Previously, there were certain PDF annotations that were indexed and searchable, but not shown in the preview pane. Also, PDF annotations placed on empty pages were completely ignored.
• Previously, the RTF bodies of Outlook emails were completely ignored. Now they are properly indexed just like plain text and HTML email bodies.

For the full list of changes in this release, please see the changelog.

DocFetcher Pro 1.18 is out. This release contains an assortment of bugfixes that accumulated since the previous release. The most notable bugfixes are:

• Previously, there were certain PDF annotations that were indexed and searchable, but not shown in the preview pane. Also, PDF annotations placed on empty pages were completely ignored.
• Previously, the RTF bodies of Outlook emails were completely ignored. Now they are properly indexed just like plain text and HTML email bodies.

For the full list of bugfixes in this release, please see the changelog.

DocFetcher Pro 1.17 is out. It's been a while since the previous release (about 9 months), mostly due to DocFetcher Server, and since then a number of bugfixes and a few small feature additions have accumulated. In total, 8 bugs and crashes were fixed, some related to indexing, some related to the Search Scope pane, and some related to the preview pane.

As for features, the new release allows setting a file size limit on the files to be indexed, e.g., "don't index files bigger than 500 MB". The significance of this size limit is that it greatly reduces the risk of the application running out of memory while trying to index enormous files. The other new features are a new "Copy With Path" entry in the context menu of the preview pane, and an encoding override setting for HTML files in the Advanced Settings file.

For a detailed listing of the bugfixes and features, please see the changelog.

DocFetcher Server 1.2 is out. This release fixes two indexing-related crashes and a major bug concerning index updates. The bug, as explained in the changelog: If a subfolder within an indexed folder was renamed, moved or removed, the files in that subfolder were not properly updated in the index, causing obsolete files to show up in the search results along the current ones. The obsolete files will disappear once you upgrade to the new release and update all your indexes.

It appears that recently, an unknown number of emails sent to the official support email address (support .. docfetcherpro.com) were lost. They were likely blocked on their way through Google's servers for unknown reasons. If you sent an email to the support address and didn't get a response, that's why. Please resend your email to the address currently listed on the support page if your issue still persists. Apologies for the inconvenience!