To do this I use a pipeline of the following modules:
1. Choose Input Files
2. Change Document Properties
3. Sanitize Document
4. Export PDF to Microsoft Word Document
Usually, dozens of documents are processed without errors, and I am satisfied with the result. However, sometimes most of the documents end up unprocessed. The PDF-Tools log shows something like
The language of PDF-XChange Pro 10.2.1.385 is English, but the language of Microsoft Windows 10.0.19045.4291 and Microsoft Office LTSC Pro Plus 2021 ru-ru 16.0.14332.20651 is russian. The paths to the files and the names of the files themselves on a disk with the NTFS file system do not contain special characters, national characters, punctuation characters or pseudographics. Resubmitting erroneous documents for processing with the same tool most often ends successfully. Unfortunately, the current interface doesn't have an easy way to do this without a lot of manual work.[11.04.2024, 11:42:26] > Export PDF to Microsoft Word Document
[11.04.2024, 11:42:26] Error: F:\Link\Networks\FidoNet\3\blstbbs\blstbbs\HISTORY.DOC: Не удается найти указанный файл.
Perhaps this has something to do with the topic "Export to Word with error" forum.pdf-xchange.com/viewtopic.php?t=40363
Convert to DOCX.pdtex —
Export PDF to Microsoft Word Document — Exemples.7z —
Upd. I turned off the “Multi-Threaded Processing Mode” setting for the tool, and almost two hundred documents that had previously generated an error during the first processing were properly converted. Even if the conversion took much longer than expected. So, most likely, this is the case. This is strange, given the small size of each document and 20 GB of free RAM while PDF-Tools is running. If, indeed, the cause of the failure is due to parallel processes, then you should think about how to make error messages more informative for users. Although, it is best, of course, to bypass this error.
