mirror of
https://github.com/ciur/papermerge.git
synced 2026-04-25 03:55:58 +03:00
[GH-ISSUE #63] OCR_BINARY seems to be useless #47
Labels
No labels
2.1
3.0
3.0.1
3.0.2
3.0.3
3.0.3
3.1
3.2
3.2
3.3
3.5
3.x
Fixed. Waiting for feedback.
Fixed. Waiting for feedback.
UX
Version 2.1 - alpha
XSS
announcement
beta
blocker
bug
cannot reproduce
confirmed
confirmed
critical
demo
dependencies
deployment
detchnical debt
discussion
docker
documentation
donations
duplicate
enhancement
feature request
frontend
fundraising
good first issue
good issue
help wanted
high
implemented
important
improvement
incomplete
invalid
investigation
kubernetes
low
low impact
medium
medium
medium impact
migration from 2.0
migration from 2.1
missing-language
missing-ocr-language
no-activity
note
ocr
outofscope
packaging
performance
popular request
pull-request
pypi
question
raspberry pi
roadmap
search
security
setup
status
task
technical debt
updates
user xp
version 1.4.0 - demo
will be implemented
will not be implemented
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/papermerge#47
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mtonnie on GitHub (Aug 11, 2020).
Original GitHub issue: https://github.com/ciur/papermerge/issues/63
It looks like the setting OCR_BINARY isn't taken into account.
The path for tesseract is hardcoded in mglib, as all other binaries.
I would really apriciate to have the ability to define binaries or paths with configuration file.
@ciur commented on GitHub (Aug 11, 2020):
You are right, OCR_BINARY setting is ignored.
I will fix this problem.
@ciur commented on GitHub (Aug 11, 2020):
Hi @mtonnie
I pushed couple of commits:
Also notice that instead of OCR_BINARY was renamed to BINARY_OCR. This is to be consistent with rest of BINARY_ settings:
All above settings can be added to papermerge.conf.py to modify path of respective executable.
Also notice that mglib version was incremented.
This code is very fresh (I just pushed). According to my couple of tests it works pretty well. Anyway, tomorrow I will update documention and perform couple of more tests.
To be continued...
@mtonnie commented on GitHub (Aug 12, 2020):
Hi @ciur,
I guess the checks in core/checks.py should also take into account the variables.
If not these checks may fail when the location of the binary isn't inculded in PATH enironment variable.
What do you think?
@ciur commented on GitHub (Aug 13, 2020):
Hi @mtonnie ,
correct! I absolutely agree. Here is the fix.
Documentation update.
@mtonnie thank you for your great feedback!
If the case above changes solved your problem with hardcoded binary paths - please close this ticket/issue.
Thank you again!
@mtonnie commented on GitHub (Aug 14, 2020):
Thanks a lot, looks good so far.
I'll test it with synlology package soon, I have focus on installation wizard the last few days.
@ciur commented on GitHub (Aug 15, 2020):
@mtonnie, yes I saw your packaging progress.I pinned that issue - as I consider it very important one. Awesome work! Thank you!