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: Tue, 18 Dec 2018 13:48:19 -0500 [thread overview]
Message-ID: <20181218184819.GA8150@rednote.net> (raw)
In-Reply-To: <CAO2sX32EbLR=QrN+e7HFxFRVJyvVCPQJoWCGbd1RV_4FyqDkxg@mail.gmail.com>
OK, this is a nit, but the O in OCR stands for "Optical," not "Ocular."
It's about the process based on vision, not on the organ that is
sensitive to light. Machines don't have eyes, biological beings have
eyes.
Linux for blind general discussion writes:
> 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.
>
> --
> Sincerely,
>
> Jeffery Wright
> Bachelor of Computer Science
> President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
--
Janina Sajka
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
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
` 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
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=20181218184819.GA8150@rednote.net \
--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).