FineReader recognition engine

Important The FineReader recognition engine will be deprecated in the next release of Kofax TotalAgility. As a result, Kofax recommends that you use the OmniPage recognition profile for both page and zone recognition for all new projects. If you have existing projects that use one or more FineReader profiles, it is also recommended that you modify those projects to use a comparable OmniPage profile.

This recognition engine is provided by Abbyy and provides optical character recognition and optical mark recognition.

You can use this recognition engine for both zone and page profiles. The FineReader Page Profile properties and the FineReader Zone Profile properties can be configured to suit your specific requirements.

Important When using the FineReader 12.2, your production machine that runs the Transformation Server module is limited to a maximum of 40 cores.

This recognition engine supports many languages with the FineReader recognition engine that is installed by default.

This recognition engine is now deprecated and is no longer installed alongside this version of Kofax TotalAgility. As a result, if you open a project that was created in an earlier version and uses one or more FineReader recognition profiles, a project warning message is displayed explaining that the FineReader recognition engine is no longer available and that you can no longer use those FineReader recognition profiles.

A corresponding OmniPage profile is created for each FineReader profile. The OmniPage copy is a replacement for the FineReader profiles, yet the FineReader profiles are still available for reference purposes. Any unsupported languages in the OmniPage recognition engine are mapped to a similar language that uses the same character-set. It is no longer possible to add new profiles or modify an existing profile to use the FineReader recognition engine.

If you attempt to perform OCR when your project is configured to use one or more FineReader recognition profiles, a fallback mechanism performs recognition using the corresponding OmniPage profile. This fallback mechanism does not negatively affect the recognition performance. When you decide to remove a FineReader profile, you are prompted to confirm its deletion and notified that the corresponding OmniPage fallback profile is renamed to match the FineReader profile that you are deleting. All instances where that profile is used, such as locators, profiles, and fields, are updated to use the renamed OmniPage fallback profile. The renaming of the OmniPage profile also takes over the internal IDs used the deleted FineReader profile. This ensures that there are no issues in scripting where references to recognition profiles is done using names and internal IDs.

When modifying an older project that uses FineReader profiles, it is recommended that any additions to that project use the OmniPage recognition profiles instead of the old FineReader profiles.