From: numerys <numerys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] OCR-menu in gscan2pdf not recognizing tesseract but shows GOCR
Date: Wed, 22 Mar 2023 20:08:46 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42932@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]
New issue by numerys on void-packages repository
https://github.com/void-linux/void-packages/issues/42932
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.20_1 x86_64 GenuineIntel uptodate rrrmFFFF
### Package(s) Affected
gscan2pdf-2.13.2_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
I installed gscan2pdf along with tesseract.
xbps-install -Su gscan2pdf tesseract-ocr-all pdftk
When gscan2pdf is ready to scan it should offer a menu to choose the Tesseract-OCR engine from. A correct menu would look like:
### Actual behaviour
The mentioned menuentry shows GOCR and only GOCR, beside it seems no GOCR package is in the Void [repository](https://voidlinux.org/packages/?arch=x86_64&q=gocr) and misses the Tesseract-entry. It looks like:
### Steps to reproduce
1. Run a desktop environment of your choice
2. Install gscan2pdf and tesseract
`xbps-install -Su gscan2pdf tesseract-ocr-all pdftk`
3. Attach a supported scanner
4. Run gscan2pdf
A [gscan2pdf.log](https://github.com/void-linux/void-packages/files/11043819/gscan2pdf.log) is attached for documentation. It does show that the a tesseract-engine is found and a gocr-engine is not found.
next reply other threads:[~2023-03-22 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 19:08 numerys [this message]
2023-03-22 21:58 ` numerys
2023-03-22 22:54 ` numerys
2023-03-24 1:02 ` numerys
2023-03-29 14:33 ` [ISSUE] [CLOSED] " Hoshpak
2023-03-29 14:33 ` Hoshpak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42932@inbox.vuxu.org \
--to=numerys@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).