FineReader recognition

This recognition engine is now deprecated and is no longer installed alongside this version of Tungsten Transformation Toolkit by default. 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.

At this time, a coordinating 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 checks for a comparable OmniPage profile and then performs recognition using that 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 users FineReader profiles, it is recommended that any additions to that project use the OmniPage recognition profiles instead of the old RecoStar profiles.