OCRFeeder

OCRFeeder is an optical character recognition suite for GNOME, which also supports virtually any command-line OCR engine, such as CuneiForm, GOCR, Ocrad and Tesseract. It converts paper documents to digital document files and can serve to make them accessible to visually impaired users.

OCRFeeder
Developer(s)Joaquim Rocha (Igalia)
Initial releaseMarch 2009 (2009-03)
Stable release
0.8.3 / March 8, 2020 (2020-03-08)[1]
Repository
Written inPython, PyGTK
Operating systemLinux, Unix-like
Available inInterface: Czech, Danish, German, English, Spanish, French, Galician, Italian, Norwegian (bokmål), Portuguese, Romanian, Slovenian, Swedish, Chinese[2]
Recognition: depends on OCR engine used
TypeOptical character recognition
LicenseGPL (free software)
Websitewiki.gnome.org/Apps/OCRFeeder

OCRFeeder is free and open-source software subject to the terms of the GNU General Public License (GPL) version 3 or later. It is available for Linux and other Unix-like operating systems.

History

Joaquim Rocha introducing OCRFeeder on Gran Canaria Desktop Summit in July 2009

OCRFeeder was started as a master's thesis in computer science by Joaquim Rocha,[3] who was later hired by Igalia, S.L. and continued development there.[4][5]

The first version was published in March 2009.[6] The OCRFeeder project was initially published and hosted on Google Code, temporarily used Gitorious[7] and now uses the GNOME infrastructure.[8] Since 5 April 2010 a software package is included in the official Debian repositories.[9]

Version 0.7 from July 30, 2010 brought image pre-processing features, 0.7.1 (November 8, 2010) enabled for scanner access from within OCRFeeder.

Features

OCRFeeder has a simple graphical user interface that is designed to the GNOME Human Interface Guidelines. It performs a Document Layout Analysis and transfers the layout to capable output formats. It searches for content areas, outlines them and guesses the content type (text or image) and processes text areas through the OCR back-end. It can use virtually any command-line OCR engine as back-end and features auto-detection and auto-configuration for all popular free engines. OCR back-ends may be either auto-configured, the necessary command line entered in a GUI dialogue or configured directly via a XML file. Scan image post-processing including de-skewing can be done.[10] All recognition results can be reviewed and edited before saving to the desired output format. Sessions can be saved and loaded. The suite also includes a spell checker.[11] OCRFeeder has built-in procedures for the post-processing of the raw OCR results returned by the OCR engine. It can remove remaining segmentation to printed lines of text, even with removal of hyphenation.

Although OCRFeeder is a GUI tool, it can also run in command line mode (as ocrfeeder-cli), which may be a useful tool for automatic document batch processing.[12] In this mode OCRFeeder uses the default OCR engine, which the user can set in the application's preferences.[13][14]

The program is written in Python and uses the GTK+ library (using PyGTK).[12] It acts as a graphical front-end for other existing tools. For example, it does not make actual character recognition itself, but uses external programs such as an “OCR engine” that is installed on the system. It can automatically detect and configure CuneiForm, GOCR, Ocrad and Tesseract as backend OCR engines.[15] Scanners are accessed via SANE. For post-processing of scanned images there is integration of the command-line tool “Unpaper”,[12] among other things. PDF files are processed using Ghostscript in the backend.

Input and output

OCRFeeder can import data from PDF or graphic files. From 0.7.1a version it supports grabbing images directly from the scanner device.[11]

The results can be saved in HTML, OpenDocument, plain text[16] or PDF[17] file formats. hOCR file output is also planned.[3] Initial formatting can be done directly in the program.

gollark: ... wait a minute, the point to point link one is just a somewhat constrained case of the general virtual channels one since *both* involve seeing which graphs are connected...
gollark: There's a lot of stuff where it has to do something like two queries and check whether it's on the "to" or "from" end and such.
gollark: Anyway, the P2P-linking solution *has* sort of led to weird code in the apiotelephone logic because it has to do stuff symmetrically.
gollark: Or my phone's internal storage or micro-SD cards or whatever else.
gollark: My programming projects quite easily fit on a cheap USB drive.

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.