-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to process pdfs - Windows #43
Comments
Hi @fraserpage I've had the same issue. In my case, the code for parsing the version string used by tesseract does not work as intended by the author. In particular, my version string was As a workaround, you can add the following bold lines to the file pypdfocr_tesseract.py found in python27\Lib\site-packages\pypdfocr: for line in ret_output.splitlines():
if 'tesseract' in line:
ver_str = line.split(' ')[1]
**if ver_str.endswith('dev'):
ver_str = ver_str[:-3]** Hope this helps, Florian |
Thanks very much @flothesof! That got it working for me. I'm still seeing the warning about imagemagick. Any clues on that one? |
Hey there! The warning is normal, the program is just telling us it would like to do Best regards
|
Got it. Thanks for your help! |
Going to reopen and fix this in source for next release. Thanks for pointing this out, folks! |
Hi - can the exe be fixed with this same patch? |
@flothesof: The warning message is actually not normal, but is reporting an error on Windows. This has been fixed in #54 |
I'm still running into this problem with the word alpha in Version 0.9.1 checkFileEndings = ['dev', 'alpha']
for line in ret_output.splitlines():
if 'tesseract' in line:
ver_str = line.split(' ')[1]
for fileEnding in checkFileEndings:
if ver_str.endswith(fileEnding):
ver_str = ver_str[:-len(fileEnding)] |
I'm seeing the following on Windows 10. You assistance would be greatly appreciated.
I see about 30 lines of the above when using trying to process a pdf with pypdfocr filename.pdf.
I see the below with any usage.
All dependencies are installed.
The text was updated successfully, but these errors were encountered: