2018.1

Table Of Contents
l ICRSettings group
l Perform ICRRecognition:Triggers the PlanetPress Capture ICRengine. For more
information, see PlanetPress Capture ICR.
l Engine Language:Define the language the ICRengine will use for text
recognition. This has a major effect on the way text is recognized, as different
languages use different databases to recognize letters, numbers and characters.
For example, accented letters are not correctly recognized in the English
ICRdatabase.
l
Fail if new ink is found on non-rewritable fields:Check to trigger the On Error tab if
and when a field set as Disable Rewriting receives ink in a new session.
l Ignore out of bounds ink data:Check to continue processing even if receiving a
PGCthat causes ink to be outside of any Capture Field to appear. This may happen if
updating the wrong document. When out of bounds ink is found, the document will be set
in the "Error"status. (see note below)
l Split PGCby document:Check to treat each document as a separate PGCfile. This
removes the need to use a Capture PGCsplitter before this task, however the
PGCSplitter remains useful when using self-replicating processes to accelerate
PGCprocessing.
l Add pattern information to the metadata:Adds advanced information in the Metadata
for post-processing:
l At the Document node, timestamp information such as ink start/end time
l At the Page node, information about each Capture Field such as its name,
dimensions, style, index, mask, timestamp and content status.
Technical
When the "ignore out of bounds ink data"option is checked, this option modifies the way
that the On Error tab reacts. When a single split is processed and generates an error,
only that split triggers the On Error tab. The other splits continue processing as usual. If
another split generates an error, it also triggers the On Error tab.
Examples &Use Cases
This task is put into effect in the following use cases and example processes:
Page 410