Table of Contents
Quick Start Guide for ABBYY FineReader Engine
Before you start: Download ABBYY FineReader Engine SDK on your computer using the link from the initial email.
1. Run product installation
2. Read and Accept the License Agreement
3. Select the program features you want installed. You have a choice to install files for integrating into 32-bit and/or 64-bit applications.
4. Enter your Trial Developer License number
5. NOTE: Your Trial License is a Standalone License. Please, DO NOT specify any License Server details and move forward.
6. Finish installation and move to the product activation.
Activation is carried out with the help of an Activation Wizard. This wizard is built into the License Manager utility. Activation information is sent as a code (Installation ID) which is generated on the basis of information about the computer on which the program is being installed. No personal information about the user or computer is used for generating this code and this code cannot be used for identifying the user.
We recommend to choose ‘Via the Internet’ method. In this case an activation is carried out automatically and takes only a few seconds. If you choose either ‘By e-mail’ or ‘By e-mail from another computer’ (your computer doesn’t have an Internet connection) you need to enter the path to the Activation File received from ABBYY in the corresponding field of the Activation Wizard.
Once the activation is complete, you may start your development project.
ABBYY FineReader Engine distribution pack contains a set of sample source code showing how to use Engine in different scenarios so you can get started faster. This section contains a short description of these samples. A detailed description of the samples can be found in the Code Samples Library provided with this distribution pack (Start > Programs > ABBYY FineReader Engine 11 > Code Samples Library).
We recommend trying these three samples:
1. Convert a document (Hello) sample shows all the steps you need to perform to make your ABBYY SDK work for you. This sample application recognizes and exports an image file using the basic objects and methods of ABBYY FineReader Engine. It is a great example of a basic code to start development of your application.
2. Engine Predefined Processing Profiles sample shows how you can easily configure ABBYY FineReader Engine with predefined processing profiles. All you need is to select the profile suitable for your task before processing and FineReader Engine will choose the best settings automatically. The sample application processes document images from the specified folder using two different predefined processing profiles so you can compare results.
3. Create an application with a graphical user interface (Visual Components sample) illustrates all OCR steps:
- Image opening
- Image analysis and recognition
- Verification of results
- Saving recognized text in RTF format
and creates a simple application with graphical user interface. It helps you to understand where a problem is, in case you are not satisfied with recognition results after processing a particular image.
NOTE: Most of the samples show the basic method to load the Engine object: Loading FREngine.dll manually using the “naked” interface. There are two more ways to load the Engine object in ABBYY FineReader Engine. Each of the loading methods has its own specifics, affecting the use of the object in different circumstances.
You can find more details about ways to load the Engine Object as well as code samples in SDK Help File: Start > Programs > ABBYY FineReader Engine 11 > Developer’s Help > Guided Tour: Advanced Techniques > Different Ways to Load the Engine.
SDK Usage Scenarios
Before you start with your application development, please read the Basic Usage Scenarios Implementation chapter in the SDK Help File: Start > Programs > ABBYY FineReader Engine 11 > Developer’s Help > Guided Tour. It describes the most common usage scenarios for ABBYY FineReader Engine. Each article contains a detailed description of the scenario, implementation advice, and suggestions on optimizing the code for specific tasks.