TESSERACT(1) | TESSERACT(1) |
NAME¶
tesseract - command-line OCR engineSYNOPSIS¶
tesseract imagename outbase [-l lang] [-psm N] [ configfile ...]DESCRIPTION¶
tesseract(1) is a commercial quality OCR engine originally developed at HP between 1985 and 1995. In 1995, this engine was among the top 3 evaluated by UNLV. It was open-sourced by HP and UNLV in 2005, and has been developed at Google since then.OPTIONS¶
imagenameThe name of the input image. Most image file
formats (anything readable by Leptonica) are supported.
outbase
The basename of the output file (to which the
appropriate extension will be appended). By default the output will be named
outbase.txt.
-l lang
The language to use. If none is specified,
English is assumed. Multiple languages may be specified, separated by plus
characters. Tesseract uses 3-character ISO 639-2 language codes. (See
LANGUAGES)
-psm N
Set Tesseract to only run a subset of layout
analysis and assume a certain form of image. The options for N are:
-v
0 = Orientation and script detection (OSD) only. 1 = Automatic page segmentation with OSD. 2 = Automatic page segmentation, but no OSD, or OCR. 3 = Fully automatic page segmentation, but no OSD. (Default) 4 = Assume a single column of text of variable sizes. 5 = Assume a single uniform block of vertically aligned text. 6 = Assume a single uniform block of text. 7 = Treat the image as a single text line. 8 = Treat the image as a single word. 9 = Treat the image as a single word in a circle. 10 = Treat the image as a single character.
Returns the current version of the
tesseract(1) executable.
configfile
The name of a config to use. A config is a
plaintext file which contains a list of variables and their values, one per
line, with a space separating variable from value. Interesting config files
include:
•hocr - Output in hOCR format instead of
as a text file.
LANGUAGES¶
There are currently language packs available for the following languages:HISTORY¶
The engine was developed at Hewlett Packard Laboratories Bristol and at Hewlett Packard Co, Greeley Colorado between 1985 and 1994, with some more changes made in 1996 to port to Windows, and some C++izing in 1998. A lot of the code was written in C, and then some more was written in C++. The C\++ code makes heavy use of a list system using macros. This predates stl, was portable before stl, and is more efficient than stl lists, but has the big negative that if you do get a segmentation violation, it is hard to debug.RESOURCES¶
Main web site: http://code.google.com/p/tesseract-ocr/ Information on training: http://code.google.com/p/tesseract-ocr/wiki/TrainingTesseract3SEE ALSO¶
ambiguous_words(1), cntraining(1), combine_tessdata(1), dawg2wordlist(1), shape_training(1), mftraining(1), unicharambigs(5), unicharset(5), unicharset_extractor(1), wordlist2dawg(1)AUTHOR¶
Tesseract development was led at Hewlett-Packard and Google by Ray Smith. The development team has included:COPYING¶
Licensed under the Apache License, Version 2.002/09/2012 |