From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: extracting text from png files
Date: Mon, 17 Dec 2018 10:34:54 -0500 [thread overview]
Message-ID: <alpine.NEB.2.21.1812171033300.9644@panix1.panix.com> (raw)
In-Reply-To: <CAO2sX32EbLR=QrN+e7HFxFRVJyvVCPQJoWCGbd1RV_4FyqDkxg@mail.gmail.com>
Thanks much, I've got both packages on my system so now it's time to
read some manuals and search for youtube tutorials to fill in the
missing pieces to learn these two packages. I didn't know these could
handle png files.
On Mon, 17 Dec 2018, Linux for blind general discussion wrote:
> Date: Mon, 17 Dec 2018 10:03:23
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: blinux-list@redhat.com
> Subject: Re: extracting text from png files
>
> What you're looking for is Ocular Character Recognition or OCR for short.
>
> I've never managed to figure out its command line syntax, but I
> believe tesseract is considered the current standard option for Linux.
>
> There's also Cuneiform, which I have actually used with some success
> in the past, but I believe its either contrib or non-free under
> Debian, so you might need to enable extra repositories depending on
> how strict your distro is about sticking to FOSS principles.
>
> I will warn you, in my experience, OCR is as likely to produce
> gibberish as legible text. A scan of a page of prose type set in a
> standard font will probably OCR well, but the more mixed text is with
> graphics, the fancier the font, and the more complicated the page
> layout, the more likely errors are. I've tried OCR'ing scanlated
> manga(Japanese comics) in the past and have gotten results that
> included unpredictible patterns of letters and numbers misidentified
> as others(S and 5, P and D, I and 1, LI and U, B and g where just some
> of the common substitutions I encountered trying to fix the OCR'd
> text), characters my screenreader could'nt identify or identified as
> characters I'm unfamiliar, and even when the text was clear,
> paragraphs out of order wasn't uncommon.
>
>
--
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
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=alpine.NEB.2.21.1812171033300.9644@panix1.panix.com \
--to=blinux-list@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).